Repository navigation
ci(release): Skip release bot merge commits - #107
Merged
Merged
Conversation
Handle Craft merges by revision as well as release branch name while preserving manual releases. Co-Authored-By: Codex <noreply@openai.com>
Prevent skipped release merges from cancelling active release preparation. Co-Authored-By: Codex <noreply@openai.com>
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.
Skip automatic release preparation when the release bot pushes a
Merge commit '…'commit. Craft merges published release revisions by SHA, so these commits bypassed the existingMerge branch 'release/…'guard and started another release attempt, often failing because there were no new commits.Keep the existing release-branch guard and allow manual dispatches, ordinary contributor merges, and generated schema updates. Scope the cancelling concurrency group to the guarded release job so skipped release-merge pushes cannot cancel an active release. GitHub still creates a workflow run for the push, but its release job is skipped.