I have this blog, right? I host it with GitHub Pages, right? To do that, I have a repo named «realistschuckle.github.com» which redirects to curtis.schlak.com when someone types it in. Turns out that migrating that to another repo didn’t work.

I created that repository back on 5 December 2011. The instructions, at that time, directed me to name it «[username].github.com» and that’s how I get my custom GitHub Pages site.

Awesome.

Because of the recent problems with GitHub Pages, I have spent a lot of time in their documentation. During that reading, I discovered that the new naming convention goes ends in «.io» instead of «.com». On the page Should I rename <username.github.com> repositories to <username.github.io>?, they instruct that

If both a username.github.io and a username.github.com repository exists, the username.github.io version is used.

To host my blog’s content, I figured I could just create a repository named «realistschuckle.github.io», host the locally-generated content from «realistschuckle.github.com», and all would work correctly.

Nope, it did not work correctly.

You see, because of that redirection that I described in the first paragraph, I included a file named «CNAME» that contained the host to which I wanted to redirect, namely, «curtis.schlak.com». When I created the new «.io» repo for my blog’s content and included the «CNAME» file, I got this automated email:

The page build failed with the following error:

CNAME already taken: curtis.schlak.com

For information on troubleshooting Jekyll see https://help.github.com/articles/using-jekyll-with-pages#troubleshooting If you have any questions please contact GitHub Support.

Crap. Well, to fix it, I figure I would just rename the «.com» repo to something else and that CNAME would no longer have a conflict. I renamed it to «blog-src». I pushed a new commit to the «.io» repo and eight minutes later received this email:

The page build failed with the following error:

CNAME already taken: curtis.schlak.com

For information on troubleshooting Jekyll see https://help.github.com/articles/using-jekyll-with-pages#troubleshooting If you have any questions please contact GitHub Support.

Crap.

So, I sent an email to GitHub support asking them to remove the CNAME association with the «.com» repo. Hopefully, then, my GitHub Pages worry will end.

For a little while.

I still ♥ GitHub.