Trigger a code review
Rovo Dev code reviews can run automatically or be triggered manually. Each repository admin can choose how code reviews are triggered in their repository.
Rovo Dev credits for code review usage are deducted from the pull request author’s allocation.
Code review options
Code review options for Bitbucket and GitHub repositories are:
Only when pull request is created—code reviews run automatically when a pull request is created, but not for subsequent commits. This is the default option.
When pull request is created and on each commit—code reviews run automatically when a pull request is created and whenever a new commit is made.
Don’t review automatically—code reviews only run when the author manually selects Analyze code in the pull request.
Manually triggering code reviews is currently not available in GitHub.
Manually trigger a code review in Bitbucket
Only pull request authors can manually trigger a code review for their pull requests. To manually trigger a review:
Go to the pull request.
In the Rovo Dev section in the Overview tab, select Review code.
Wait a few minutes for the review to complete, then refresh the page.
Rovo Dev will add comments if it finds potential improvements or bugs. If Rovo Dev doesn’t have any feedback, it won’t leave any comments.
Each commit can only be reviewed once. To avoid duplicate reviews, you can’t trigger a code review manually if your repository is set to run when pull request is created and on each commit.
Was this helpful?