Why does BitBucket not allow merge strategies to be applied to specific branches in a repository? Traditionally, I would handle this through my own scripting, and hooks; however, there is no such granularity with BitBucket. This is what I would like to be able to implement:
master: --squash --ff-only
feature/bugfix->develop: --squash --ff-only
Unfortunately, I have no way of managing this using BitBucket. I realize that the newest version allows the merge strategy to be directed by the integration manager. Unfortunately, in an organization with over 200 developers, and 20 integration managers, this becomes too chaotic, as incorrect merge strategies will be chosen causing major issues to our repository management.
Is there any consideration for addressing this?
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events