Add determinate merge strategies for explicit branches

[John Bain]

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

release->develop: --no-ff

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?

Thanks,

John