Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-5147

Allow merge checks such as minimum reviewers to be configured by branch type or pattern

XMLWordPrintable

    • 29
    • 9
    • 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.

      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.

        1. bbminreqbuildsperbranch.zip
          14 kB

              Unassigned Unassigned
              f4787cf404c1 Matt Walker
              Votes:
              68 Vote for this issue
              Watchers:
              55 Start watching this issue

                Created:
                Updated: