I\'ve forked a repo that has gh-pages
set as it\'s default branch. They\'re hosting it on a custom domain, so there is a custom CNAME
file.
I\'m
Switch to the gh-pages branch on that forked repo. Then remove the CNAME
file. That should fix this problem.
You can get those emails because your forked repo tried to send the GitHub server the same CNAME
settings as another project. (In your case, the upstream repo you forked from.)
I would suggest renaming the "branch" in your fork to something other than gh-pages, that should prevent it from triggering builds, but will still allow you to pull request to the gh-pages on the upstream parent.