Workflow: Auto-publish all branches to gh-pages #149
Merged
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
nicolo-ribaudo
approved these changes
Dec 9, 2024
There was a problem hiding this comment.
I was looking for a solution that avoids accumulating folders in the gh-pages branch, but it turns out that it's not worth the complexity.
I changed this repo's settings to prevent creation of new branches, so that we are forced to always open PRs from our own forks and thus get the preview in our own repos.
github-actions bot
added a commit
that referenced
this pull request
Dec 9, 2024
SHA: 6521be3 Reason: push, by nicolo-ribaudo Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
This CL changes the auto publish workflow to build all branches (except
gh-pages) and put the result into<branch name>/index.htmlon thegh-pagesbranch. Themainbranch is still published to the rootindex.htmlthough.This is very convenient for forks, since it's straight-forward to preview PRs.