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.
Proposed Changes
Main change: allow the "Publish" workflow to publish to a tag other than
latest
, depending on the branch name and the state of the "Prerelease" checkbox in GitHub's release UI.Additional changes:
commitlint
now runs as a separate workflow instead of as part of the CI workflow, so you can tell the difference between acommitlint
failure vs. a build/test failure.Reason for Changes
This allows the
spork
branch to publish to thespork
tag on npm, making it easier to test on staging. Other branches are likely to want this soon, so I pulled this out of thespork
branch so we don't need to wait for all thespork
QA to finish before those other branches can use this change.Test Coverage
I've already used this workflow from the
spork
branch.