Closed thomasyu888 closed 5 years ago
That's expected! The file CNAME
file in this repository has that. If you fork and try to build based on the same CNAME, then you would get this warning. We chould add this to the contributing section though - but this method of 'testing' isn't recommended. You should use the documentation on how to build locally. If you are only making simple Markdown changes, then previewing in any Markdown editor should suffice as well. Thanks!
I see. I didn't try to build though. The only thing I did was fetched upstream gh-pages
and created my own gh-pages
branch so it can always mimic that of upstream gh-pages
. Good to know.
You inherit the settings on the repository as well, it seems. Which means GitHub pages is enabled on the gh-pages
branch of your fork. Then, anything you commit to it will automatically trigger a build (it's a built in continuous integration and deployment system).
You can change that by disabling GitHub Pages on your fork in the main settings of the repository!
I get an email with this content: