Why can't I disable Github Pages?

I understand you can by deleting the gh-pages branch, but why is that needed? There is a button to disable gh-pages, but it’s greyed out. It’s confusing.

xgAZYjr

11 Likes

I think it’s to account for legacy behaviour. Before this option was avialable you could just use a gh-pages branch to trigger GitHub Pages to render. Anyone who creates a branch locally with the same name and pushes it up should get a Pages site automatically. Best thing to do is to branch gh-pages to a name other than this and then turn it off and delete the old branch.

6 Likes

There is a button to disable gh-pages, but it’s greyed out. It’s confusing

@matiaspi wrote:

I understand you can by deleting the gh-pages branch, but why is that needed? There is a button to disable gh-pages, but it’s greyed out. It’s confusing.

I agree.

8 Likes

What if you fork a repo with GitHub Pages and you need to keep the branch to be able to create Pull Requests?

Every time I push to my fork it sends me an EMail saying the custom domain is taken.

I tryed changing the domain for my fork but that didn’t help. I can’t disable it as well.

So basically I’m stuck.

Any ideas?

4 Likes

Thanks for the explanation of how it’s related to legacy behavior. Not being able to disable GitHub Pages when we have a gh-pages branch has become an annoyance for our project. Frankly, I don’t understand why the “Disable GitHub Pages” options needs to be innaccessible. As long as it is opt-in, I don’t see how it interferes with any legacy behavior or repositories. 

1 Like

@srfrnk wrote:

What if you fork a repo with GitHub Pages and you need to keep the branch to be able to create Pull Requests?

Every time I push to my fork it sends me an EMail saying the custom domain is taken.

I agree. As of 2019/06/12, exactly the same thing is happening to me.

GitHubHelp didn’t help either. Because  deleting the “gh-pages” branch is not an option since I’d like to contribute translate their web pages.

My current workaround is to switch the GitHub Pages’ source to “master” branch, which is also grayed out but choosable. Since this branch doesn’t contain the “CNAME” file.

But still, this exposes the forked master to myname.github.io and I feel uncomfortable. 

What I want is just to choose “None” to disable the GitHub Pages. :sob:

  • Browser: Chrome 74.0.3729.169 + macOS: Mojave (OSX 10.14.5)
3 Likes

Dank acktivez cont