Sorry about the trouble.
We've had an issue previously with incoming build results in rapid succession which confuse the auto-merge process. Please have a look through this ticket and see if that matches your problem. Basically an incoming build result can trigger an auto-merge (if criteria are satisfied) - another incoming build result within a few ms would create a race condition as it finds the PR not yet merged.
If you can't resolve the problem please do the following:
Turn on workzone logging with
curl -u admin -v -X PUT -d "" -H "Content-Type: application/json" http://bb-host:7990/rest/api/latest/logs/logger/com.izymes.workzone/info
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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