You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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?