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?
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
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 ...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot