Pull request - non-ff git merge required?

When I initiate a pull request, bitbucket only gives me the option to do a non-fast-forward merge to bring changes in. Why is this? I can see why some people might like it that way, but it makes the history less readable too. Are there any options where I can either request a fast-forward merge or rebase if possible when accepting a pull request?

1 answer

0 vote
Jason Worley Atlassian Team Apr 19, 2013


This is a question we field on occassion. We actually leverage Git's native behavior. In other words, by default, the client will throw an error and prompt users add --force.

That being said, you can opt to toggle this flag.

I hope this response was helpful.

Happy Coding! :)

Jason | Atlassian

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
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,018 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