-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
unable to prevent removal of CNAME #179
Comments
this wont be a good long term solution because of filenames changing each time the contents change, but the --remove flag isnt working as expected. this should at least prevent the removal of CNAME with every deploy until i hear back on tschaub/gh-pages#179
I needed to prevent it from removing a |
Same here, it isn't working. |
I'm not sure why but "-a" seems to fix the issue. "deploy": "gh-pages -d build -a" |
FYI, |
for those finding this thread, it is worth being aware that as nice as github pages is for simple things, those two issues have motivated me to move most of my static sites to netlify instead. |
Gatsby will copy any files from static/ directly to the build output folder. This is useful to preven CNAME from being removed by gh-pages, see tschaub/gh-pages#179
I ran across your suggestion to use
--remove
with negation to prevent removal of specific files when using the cli, but have been unable to get that working.Is that approach still supported/recommended?
The text was updated successfully, but these errors were encountered: