Before you start
- Use a harmless change in a test repository. Ask someone who can inspect the target branch rules and arrange for a reviewer and a contributor without bypass permissions.
- Record the repository, destination branch and revision you intend to review.
- Check Bitbucket availability
Data and access
Compare approval rules
Bitbucket Cloud
Open Branch restrictions and check the rules that match the destination branch. Look for the required approval count and successful builds on the latest commit. The Premium setting Prevent a merge with unresolved merge checks enforces those checks. Without it, Bitbucket warns about unresolved checks and can still allow the merge.
Check. On the current pull request, record the destination rule, the revision the builds cover, and whether the checks block a merge.
Azure Repos
Open Branch policies for the target branch. Check the minimum number of reviewers and whether Build validation is Required. Review the branch's permissions for bypassing policies when completing pull requests and when pushing. On the test pull request, inspect the approval and build results for the current revision.
Check. The current revision shows the required reviewers and build result. Record any bypass permission separately.
Gerrit
Open the change and select its current patch set. In Submit Requirements, inspect the rules and the votes that satisfy them. Check who has Submit access and whether any requirement was overridden. A new patch set may affect votes, depending on the project's label rules.
Check. Review the current patch set’s Submit Requirements and the votes that satisfy them. Record an override if one is present.
SourceHut
On a test project's mailing list, open the latest revision of the patch series and read the review thread. If the project records a patch status, check it alongside the discussion. Compare the reviewed patch with the commit on the destination branch after the maintainer applies it.
Check. The mailing-list review identifies the patch revision the maintainer applied. Compare its changes with the destination commit.
Check the result
For an enforced merge rule, check that the test change is blocked before the requirement is met, then record the authorized review and merge. If you submit a new revision, repeat the check on that revision. For a mailing-list workflow, record the reviewed patch and the resulting branch commit separately.
Check. Keep the links to the blocked and later allowed results for the same test revision. For SourceHut, keep the reviewed patch and destination commit.
Check your result
Keep the link to the exact review and record the destination commit. For enforced rules, keep both the blocked and allowed results for the test branch.
If you get stuck
The change landed before review
Check which rule matched the branch, whether the check was enforced and whether the acting account had a bypass. On SourceHut, check who can write to the destination branch and how the project records maintainer decisions.