Reviewing pull requests that two or more changes have been made in a single file, some times, is not that simple. Even more when those changes aim the same section of code.
So, if each modified file in the pull request interface could have their related commits grouped in a (header or footer) section next to them, the reviewing task could become easier, considering that the reviewer could fetch the related commits for the evaluated file such that he/she could better understand the code "evolution".
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot