If Git supports it, then Bitbucket supports it... What are you trying to do? Usually a changes in Git only has one commiter. Git (and therefore Bitbucket) will track change sets levels and a push to Bitbucket (or any other remote repository) can have multiple commits in it...
You need special support on your web.
We encourage the use of Co-Authored-By: name <firstname.lastname@example.org> in commit messages to indicate people who worked on a particular patch. It's a convention for recognizing multiple authors, and our projects would encourage the stats tools to observe it when collecting statistics.
As result, if you have something like that in commit message, you should insert link to this guy as second commit author (I am about the web-interface)
That would be an improvement request you need to make.
You'll need to explain how to implement it when
a) The co-author is NOT the committer, which is what the field is for
b) The co-author field is a random bit of text that may well not be a known user
So, you use "author" and "email" to detect commit author (I checked it, I can set author/email of my co-worker and commit would be linked to my co-worker profile).
If you see "Co-Authored-By:<TEXT>\n" in commit message, you should try to parse it to "USERNAME <EMAIL>" and than link USERNAME/EMAIL exactly as you make it for commit author/email
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