Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Unresolved
Fix Version/s: None
Component/s: Pull Request - Merge
Labels:
- iw

UIS:
25
Feedback Policy:

We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

We have a repository with a review gated merge policy (requires 2 reviewers to approve before merge to master is allowed). I recently branched another developers feature branch and made changes, I created a pull request so that they would get a notification that they should merge and update their branch. However... what happened was that stash then required two reviewers to approve the PR. The gated reviewer stetting is global in a repo.

Imo, it is desirable to whitelist / blacklist branches for requiring review. In my case we would whitelist 'master' as the only one requiring review. Going the other way, globs would be useful, e.g. blacklist 'feature/*' as not requiring review.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

bbminreqbuildsperbranch.zip
14 kB
04/Jun/2019 8:01 AM

Issue Links

is duplicated by

BSERV-5257 Checks for merging pull requests - per branch

Closed

BSERV-5467 Allow # approvals to be specified on pull request basis

Closed

BSERV-7845 Stash: per-branch pull request settings

Closed

BSERV-8120 Support different pull request rules per-branch.

Closed

BSERV-8144 "Minimum successful builds" for pull requests of specific branch

Closed

BSERV-8880 Allow per-branch Pull Request requirements

Closed

mentioned in: Page Loading...; Page Loading...

(1 is duplicated by, 2 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Matt Walker

Votes:: 67 Vote for this issue

Watchers:: 51 Start watching this issue

Dates

Created:: 19/Aug/2014 1:17 AM

Updated:: 20/Feb/2024 3:18 AM