Unable to "Merge without waiting for requirements to be met (bypass rules)" #228
CoreyKovalik
started this conversation in
Feedback
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Duplicate issues
Desired outcome
Have the same functionality to "Merge without waiting for requirements to be met (bypass rules)" for GitHub Stacked PRs.
The problem & reproduction
When a PR at the bottom of the stack is out-of-date with the base branch (
mainin this case) and is approved, you can merge it if your branch protections allow you to do so. All PRs above it in the stack lose their approval due to the rebase (this is expected).Switching over to the next PR in the stack that has now become the bottom of the stack, it's unapproved (which is expected), however, you lose the ability to "Merge without waiting for requirements to be met (bypass rules)".
The workaround solution was to:
Beta Was this translation helpful? Give feedback.
All reactions