My team is currently conducting reviews with pull requests in Bitbucket. Why would we need Collaborator for reviews?
For some teams, conducting code review through pull requests in Bitbucket is enough, especially for small changes. While simple reviews in Bitbucket might be convenient, it can dramatically limit your team's code review process. Through a Bitbucket integration, Collaborator enables teams to customize their reviews with custom fields, workflows, checklists, and participant rules. Your team can specify comments versus issues so you can capture metrics on your process, like defect type and severity, inspection rate, and lines of code reviewed, and use the review as a quality gate. Collaborator also enables your team go beyond just reviewing code to also review different document types. If you want to build a review process that includes multiple artifact types and drives continuous improvement, it is easy to integrate Collaborator with Bitbucket and ensure quality code is being merged.
When is a review created using the Bitbucket integration?
A review will be created when either a pull request or push/commit is made to a branch that Collaborator is told to track.
How do I get to the review in Collaborator once one has been created by the Bitbucket integration?
When a review is created by a pull request or push/commit, Collaborator will leave a comment with a link to the review on the pull request OR push/commit.
Can I create a review for a pull request from Collaborator?
No – the review is created when the pull request event occurs in Bitbucket with a destination branch monitored by Collaborator. To ensure reviews are created for all branches that need a review prior to merge, change your branch settings for that repositories integration.
Who’s account will the Collaborator review be associated with when it is created by the Bitbucket integration?
Collaborator will try to associate the Bitbucket user that initiated the pull request / commit with a Collaborator user. If the Bitbucket user name matches a Collaborator user name, the review will be created under that Collaborator account. If Collaborator cannot find any users that match the Bitbucket user name, it will look to see if any users have mapped their Collaborator user name to their Bitbucket user name; if it finds a match, the review will be created under that Collaborator account. If Collaborator cannot find any users who match the Bitbucket user name, or are mapped to the Bitbucket user name, the review will be created under the Admin user.
As I continue to develop, can I update a review with new commits after a review is created?
If a review is created by a pull request, as you merge code into your pull request, the Collaborator review will be updated.
What happens if I perform rebasing operations on the commits involved in my pull request after a review is created?
The Collaborator review will update itself to match the git history of the pull request. For example, if you squash several commits in a pull request, the Collaborator review will reflect that. We won’t remove comments left on versions of a file that have been rebased out of a review.
What happens if I merge in upstream changes to my pull request after a review is created?
The Collaborator review will update accordingly, and by default, will not highlight these changes in the diff viewer.
What happens when I leave comments on a Bitbucket PR? How about a Collaborator review?
Comments will propagate from Bitbucket to Collaborator, but will NOT propagate from Collaborator to Bitbucket.