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

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

XMLWordPrintable

    • 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"

      Latest update from Atlassian: 2025-02-19

      It is now possible for the "Maximum number of commits behind destination branch" merge check to be set to zero (0). This effectively allows enforcement that the source branch is up to date with the destination.

      Dave Parrish
      Product Manager, Bitbucket Cloud 

              dparrish Dave Parrish [Atlassian]
              641e77b2eb21 Patrik S (Inactive)
              Votes:
              131 Vote for this issue
              Watchers:
              72 Start watching this issue

                Created:
                Updated:
                Resolved: