Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-22431

Ability to force the source branch to be synched with destination before merging


    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently, in Bitbucket Cloud, a merge check can be added to define the "Maximum number of commits behind destination branch", however, the minimum value that can be set is 1 commit behind.

      It would be great to have the ability to define a value of 0 (zero) commits behind, to make sure the source branch is synced with the destination branch before the Pull Request is merged, or have a Merge check specifically to "Branch is up to date with target"

            Unassigned Unassigned
            641e77b2eb21 Patrik S
            117 Vote for this issue
            59 Start watching this issue