fix: stop claiming non-release after ALLOW_RELEASE_MERGE bypass#213
Merged
Conversation
When the strong release guard detects a release PR and ALLOW_RELEASE_MERGE=yes is set, exit after the bypass message. Do not print the generic "does not appear to be a release PR" line, which was misleading after a real bypass. Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
SebTardif
enabled auto-merge (squash)
July 24, 2026 13:27
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
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
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.
Summary
After
ALLOW_RELEASE_MERGE=yeson a release PR, the guard printed both the bypass notice and "does not appear to be a release PR". Exit after the bypass message so agents do not misread the outcome.Test plan