fix(backflow): stop the App from stamping the human merge ack - #20
Merged
Merged
Conversation
backflow:merge-commit means a person will merge with a merge commit, not squash. The revfleet-backflow App was applying that label to its own canonical PR, which forged the acknowledgment. Auto-merge stays MERGE-only. Ancestry mode is unchanged.
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
2 participants
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
Stops the revfleet-backflow App from applying
backflow:merge-commitwhen it opens the fallback PR. That label is a human acknowledgment. The App onchore/backflow-main-into-testis recognized by the revealui guard instead. Auto-merge remains merge-method MERGE. Ancestry mode is untouched.The revealui caller pin is bumped in the paired revealui pull request after this lands on
main.Test plan
backflow-reusable.yml