You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
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
Announced in this blog, this holiday season we’re celebrating all things CI/CD and between now and the end of 2019 we’ll be showcasing content, use cases, feature announcements and more. One featur...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events