Use gh‑pages branch
#24
Closed
Conversation
This file contains hidden or 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
ExE-Boss
force-pushed
the
feat/use-gh-pages-branch
branch
from
874ee0c to
5147d13
Compare
|
Why is this an improvement? It's simpler imo when there's only a single branch for the raw and rendered spec. |
|
It ensures that the |
|
Right, but I find that more complex than having one branch for the entire proposal repo. |
|
I strongly agree with @ljharb about keeping all contents in a single branch, but would personally prefer use of /docs rather than dumping rendered output at the top level. |
|
Closed by #32. |
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 makes the build result be deployed to the
gh‑pagesbranch.The configuration is based on https://github.com/tc39/proposal-realms/blob/master/.github/workflows/publish.yml