Add note about GH Pages redeploy #16
Conversation
I changed `master` to `main` on a `username.github.io` repo and the site went to 404. I assume it was DNS related and would solve itself and went to sleep. The site was still down in the morning, so I edited the `index.html` to add a single character change and merged to trigger a deploy. This fixed it. I'm shocked that GitHub doesn't just perform a one-time deploy of GH Pages after a branch name. Especially in a scenario where you're going from `master` to `main` on a repo ending in `.github.io`. But really it should just do that anytime the branch used for GH Pages is renamed.
|
@willsmythe can you comment on this? |
|
There is now a note added to the alert when you go to rename your branch. Though this is pretty easily missed and it would still be useful to have this documented for those after the fact.
|
|
Fun fact! I just changed that branch from |
|
Instead of adding a single space (or some other meaningless) for this, you can just use the |
I changed
mastertomainon ausername.github.iorepo and the site went to 404. I assumed it was DNS related and would solve itself and went to sleep (using a CNAME file). The site was still down in the morning, so I edited theindex.htmlto add a single character change and merged to trigger a deploy. This fixed it.I'm shocked that GitHub doesn't just perform a one-time deploy of GH Pages after a branch rename. Especially in a scenario where you're going from
mastertomainon a repo ending in.github.io. But really it should just do that anytime the branch used for GH Pages is renamed. Forcing all users to know about this weird edge case and having to add a space to a file to fix it is very hacky.Until this can be automated by GitHub staff, it should at least be documented.