Two questions about pull requests with stash.
Current stash documentation describes the following behavior for comments as pull requests are updated:
Participants can commit new changes to the branch. Stash auto-updates the Commits tab of the pull request, so you can see exactly which commits will be merged. Stash is smart about comments, moving them along when lines are added or removed. If a line with a comment gets removed, you can still view the comment in the activity, but Stash marks the diff as outdated to let you know that this piece of code has been changed in recent commits.
Would it be possible instead to simply leave comments on the "commits" tab, rather than the "diff" tab, which is silo'ed per commit? In this case, comments could be immutable, and would be easier to track the iterative feedback/code change loop. This seems to be the way Gerrit handles the evolution of a code review, as you can see for example here.
In Stash 2.3, it seems like every individual comment sends an email. Would it be possible to have all comments batched as a single piece of feedback, triggered when the pull request is approved or denied? Again, this is how Gerrit operates -- comments are 'drafts' until the reviewer submits with a score.
If these are reasonable questions, I am happy to submit them as feature requests for Stash via Jira.
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