ci: continuous release-plz #280
Merged
+9
−27
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
robjtede
force-pushed
the
release-plz-continuous
branch
from
b06a039
to
383e6b4
Compare
NobodyXu
approved these changes
Jun 9, 2024
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 sets up the automatic release PRs so that they are drafts, which is the lowest-friction workflow in my experience, due to some annoying GitHub limitations that attempt to prevent "bots" triggering CI runs recursively.
Explanation, aside: imagine the CI "actor" opening/updating the release PR, plus then if it auto-merged, etc, etc. GitHub is too dumb to properly detect if this is a problem or not so they seem to just disallow it entirely.
The lint
types: [opened, synchronize, reopened, ready_for_review]needs placing on all workflows with "required" jobs so that they run when we un-draft (a non-bot trigger).