ci: enforce changesets on pull requests#610
Merged
Merged
Conversation
commit: |
brendanjryan
force-pushed
the
brendanjryan/enforce-changesets-ci
branch
from
ba35d52 to
268d287
Compare
brendanjryan
force-pushed
the
brendanjryan/enforce-changesets-ci
branch
from
268d287 to
d413f7a
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Motivation
Package-impacting pull requests should fail normal CI when they omit a Changeset, while generated release pull requests and intentionally unreleased changes need an explicit escape hatch.
Summary
Verify / ChecksCI job.HEAD^1) as the comparison point with a shallow depth of 2.changeset-release/mainrelease pull requests titledchore: version packages.skip-changesetlabel to bypass the check, with PR CI rerunning when labels change.Key design considerations
mainrelease workflow unchanged.