Repository navigation
MINOR: Require approval and deletion after merge - #3922
Merged
Merged
Conversation
This PR adds three things: - Automatic deletion of the branch after merge, to keep things tidy. - Require approval before merging, to avoid merging things without a review. Or committing directly to main through the UI, without going through a PR. - Require a linear history. I think we already do this by enforcing squash above on line 31, but good to make it explicit as well.
wgtmac
approved these changes
Nov 1, 2026
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.
Rationale for this change
This PR adds three things:
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?