You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think this might be preferable to current behavior of initializing an empty local repo and force pushing it onto github. The flow would be
if gh-pages branch exists
stash local changes
pull from remote
apply stashed changes
push
This would preserve gh-pages commit history. It would also prevent forcible overwrite of other files in the gh-pages branch that are not used by gitbook, such as supplementary data files, or a CNAME file (which is necessary for custom domain name using github pages). Such files currently get forcibly overwritten in the current behavior, even if added to .gitignore file.
The text was updated successfully, but these errors were encountered:
wabarr
changed the title
publishGitbook() should check for existing gh-pages branch on github
publishGitbook() should check for existing gh-pages branch on github
May 6, 2014
I found your related discussion of this with ramnathv. Maybe another option is to have an option to add other files (like the CNAME file) when publishing to github. GitbookIO/gitbook#106 (comment)
I think this might be preferable to current behavior of initializing an empty local repo and force pushing it onto github. The flow would be
This would preserve gh-pages commit history. It would also prevent forcible overwrite of other files in the gh-pages branch that are not used by gitbook, such as supplementary data files, or a CNAME file (which is necessary for custom domain name using github pages). Such files currently get forcibly overwritten in the current behavior, even if added to .gitignore file.
The text was updated successfully, but these errors were encountered: