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
Hi Bitbucket community friends,
We'd heard that people loved the branching model in Bitbucket Server, because without it inconsistent naming results in slower workflow and general confusion. Then, even when you’ve decided on a naming scheme, it's a pain to keep typing the same thing, and errors easily slip in.
Basically, when enabled, your default branch type names are set to Bugfix, Feature, Hotfix, and Release (which can be individually turned off, or edited, to match your naming convention, also you can specify other if you need to create a one-off branch with a different name).
Then if you combine this with Branch Permissions, you can make sure all branches of a certain type can only be merged by nominated team members, which reduces the "oooops! I merged to master!!" panics.
As an added bonus if you’ve got Jira and Bitbucket connected, your new branches in Jira Software will automatically select the relevant branch type for the Jira issue type, for example: bug →
bugfix/ and story →
We’ve made this feature available for all Bitbucket repos. But we don’t want to surprise your team in the middle of working on an existing repo, so you’ll need to specifically enable it to enjoy the benefits. However, new repos will have the feature enabled by default (this can be changed in repository settings).
This is the first step in a set of features to help your teams work with branches more easily, so we are really keen to hear your feedback! You can leave it either here in the comments or use the Feedback button in Bitbucket. Will this make things easier for you? Have you been waiting for it? Is it not quite there yet? How can we help you more?
Looking forward to hearing your thoughts!
Bitbucket Content Designer