-
Suggestion
-
Resolution: Done
-
None
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"
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
- depends on
-
BBCEEP-3890 Loading...
-
BBCEEP-3943 Loading...