In our BitBucket configuration it is possible to add changes to the pull request and merge it after the initial approval is given.
1) Create a pull request from the dev branch to master
2) Approve it by someone else
3) Push more changes to the same branch dev branch. The changes now appear in the same pull request
For some reasons, the new changes do not require an approval and can be merged now along with the main change.
Can we change BitBucket configuration in such a way that every new change to the pull request resets the number of approvals to zero?
The free Bitbucket Server Auto Unapprove Plugin probably does what you're looking for.
It's free, open source, and maintained by Atlassian. In a couple weeks I'm hoping it will stop dropping approvals for immaterial changes (like clean rebases, clean synchronization merges, amended commit messages, etc).
(I'm the author of the paid Bit-Booster for Bitbucket Server add-on. If you check out my add-on, you'll see why I decided to send a pull-request to the Unapprove add-on. Customers were reporting bugs against *my* add-on to say my Rebase button was dropping their approvals!)
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