'How to do a good code review in Bitbucket
I have used a few code review programs. I am now using pull requests in Bitbucket. I am expecting a certain process:
- Create review (ie pull request)
- Comments are added by reviewers. ( am used to a graded system where someone can mark the change as a bug which needs to be fixed before being merged)
- The review is sent back to the originator who fixes any problems that are marked
- (!!)The originator pushes their changes to their branch and then the code review is done again by all reviewers who then approve or reject the new changes.
- With all things being good, the review is approved and then merged.
What I am wondering about are steps 3 and 4. There seems no grading to the comments and there seems to be no way for the originator to see quickly the comments (in some condensed format). Also, how do new changes update a pull request? Is this just missing from the Bitbucket system or is there a way to achieve this?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|