Retain the gh-pages branch history #25
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pushing an innocuous commit (56682a0) appeared to reset the repository custom domain setting, making the book inaccessible. I don't know what caused this issue, but we previously deleted the existing gh-pages branch every time the book was updated. This commit makes the deploy action retain the branch history, and hopefully the custom domain will not be affected by future commits.
|
I just pushed another commit to master (0ab7164) and once again the custom domain setting was reset. |
|
Some searching led me to this issue (also documented here) so apparently we need to create a |
|
I've addressed this in #26 instead, which also adds online previews of each pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pushing an innocuous commit (56682a0) appeared to reset the repository custom domain setting, making the book inaccessible. I don't know what caused this issue, but we previously deleted the existing gh-pages branch every time the book was updated. This commit makes the deploy action retain the branch history, and hopefully the custom domain will not be affected by future commits.