Push output directory to gh-pages branch #9
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
|
Have you tested the changes to see if they work as expected? |
|
Yes, I am using this for https://github.com/apes-suite/apes-suite.github.io and it produces the content over at https://apes-suite.github.io/ |
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.
Maybe I'm using this wrongly. But to me it appears like the idea is to push the generated page only to the
gh-pagesbranch. This was however changed by PR #4. So now thegh-pagescontains the complete repository not just the generated website. And as such the pages do not look as expected when github publishes the branch. This change reverts this to, what I think is the expected behavior.