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

newest release branch not showing up in automerge

Satish Panpatte
Satish Panpatte Apr 20, 2017

I have created a release branch QS1704 from master and release branch QS1705 from QS1704. I have enabled automerging ON. I created one feature branch "feature/xyz-abc" from release/QS1704. I raised a pull request from feature branch to release QS1704 branch. When I click merge button. Merge flow I see is feature->QS1704->master where as I was expecting feature->QS1704->QS1705->master (since I have enabled automerging). Can you please help me why QS1705 is not shown in merge flow?

 

Answer
Watch
Like Be the first to like this

0 answers

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Piotr Plewa
 Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

2,011 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you