Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Automatic merging from master to release branches

BrunoOliveira25
BrunoOliveira25 Oct 24, 2023

Hello,

Currently I have two branches: 

  • dev - for development purpose
  • release/common - to maintain a common release

For this two ones, I have activated the automatic merge and it working fine.

Now I want to add a new one called release/common_v5 and I want the behaviour to be:

  • When I open a Pull Request to release/common, it should be merged into itself, release/common_v5 and dev
  • When I open a Pull Request to release/common_v5, it should only be merged into itself and dev
  • When I open a Pull Request to dev, it should only be merged to dev

How should I maintain this in Bitbucket branch settings so I can accomplish this outcome?

Best,

Bruno

Answer
Watch
Like Be the first to like this
93 views

0 answers

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS
AUG Leaders

Atlassian Community Events

See all events