Details
-
Suggestion
-
Resolution: Won't Fix
Description
If I have branch A with 1 commit and Branch B based on Branch A with 1 more commit, and create a PR for Branch A to Branch C and another PR for Branch B to Branch C bitbucket creates 2 PR where the first, PR BCLOUD-1, has 1 commit and the 2nd, PR BCLOUD-2, has 2 commits (incl. the one in the other PR).
If PR BCLOUD-1 gets merged, the PR BCLOUD-2 gets updated to remove the commit that was merged from PR BCLOUD-1, and end up having a single commit, the one that was specific to PR BCLOUD-2.
This is ok, but I would like a more advance behavior, where BitBucket would recognize that the PR BCLOUD-2 depends on PR BCLOUD-1 and do not display the first commit as part of PR BCLOUD-2. That PR BCLOUD-2 can only gets merged successfully if PR BCLOUD-1 is merged first (or deleted).
This would allow a better workflow where changes are stacked together to be merged into the same branch.