if we merge a feature branch into, say, our develop branch, then push develop, the open pull request for the feature branch is marked as merged - which is great. However the activity which is created on the PR doesn't contain the merge commit id on develop, where as if we click Merge on the PR, we go get this information. Is there anything we are missing? I'm guessing we could create a PullRequestMergedEvent type handler to add this information ourselves.
That sounds like a totally reasonable request, though there may be some technical reason why the merge commit is difficult to determine programmatically. I've raised https://jira.atlassian.com/browse/STASH-7028 to track the issue - please follow there for updates from the Stash team.
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