My company uses BitBucket Server for our git repositories. In the UI, if you click the "approve" button on a PR that's already been merged, the message you get is "Participants may not update their status on merged pull requests."
The fact that it's already merged is not the first thing the user sees, and is not highlighted, and therefore easy to miss because the verbiage used is passive. It would be much clearer if it used more active and clear language directed at the user, such as "You cannot approve this pull request because it has already been merged."
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