I am working to understands the workflow for pull requests. Here is what I have discovered along with questions. If this could be validated, it would be appreciated.
My questions and possible misunderstanding happen if there are any cycle updates because of the review.
It seems after a request is declined, it's life ends. The developer would need to submit another request for the review to continue.
It also seems that the files changed in the review appear only once. Here we have the opportunity to comment on lines of code, but where there is a code review change cycle, the changed files are not available in a single request.
If this is true, thenb any code review cycle that involves remediation because of the review will require multiple declines and subsequent requests.
Am i close? Any feedback would be appreciated as i work to understand this tool.
You're right that the "decline" option kills pull requests forever. Bitbucket automatically updates open pull requests with new commits, though, so if the reviewers leave the pull request open through several commits then the pull request will show all net changes.
With that in mind, I'd suggest a slightly different approach to the code review:
With this approach, the pull request remains open for the duration of the review process. You'd save "decline" for things which will never, ever happen.
Does that help?
Thanks for the response. I did think of that. From what I can see, the files that are changed by the second and later updates by the developer do not appear in the individual pull request UI.
This means that the reviewers must manually go and look up the files that changed. Also, there no way to comment on individual lines of code. I really like that capability.
Is this correct or am I missing something?
Thanks again for your help.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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