The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
Strategy for enabling both fast forward merges and clearing of approvals on change
Here is the scenario that I would like to implement:
Currently, we have fast forward disabled, and approval clearing is enabled.
We have a large number of developers on our project, so we're usually dealing with 20-30 pull requests a day.
The issue we run into is that when a PR is merged, subsequent open PRs start showing merge conflicts. The submitter then has to rebase, then push. This clears all approvals, so the developer has to get approvals all over again.
What I would like to do is leave approval clearing enabled, and also enable fast forward.
But the two following business rules apply:
- Approvals must not be cleared on a fast forward merge in which no other changes were made.
- Approvals must be cleared if there were changes other than those needed to satisfy a fast forward merge.
Does Bitbucket know that a particular commit is a fast forward? And can it tell if additional changes have been made outside of the fast forward, but submitted with the fast forward commit?
Does anyone have any ideas on where I can start with this? Or basic logic that needs implemented in Bitbucket?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.