When Archie reviews
Archie reviews a pull request in two cases:- On request. Someone selects Request review in Reviewers and chooses Archie Reviewer, or selects Request Archie review on the pull request.
- When the pull request is created. The project setting Code review controls this.
The Code review setting
Code review is a project-wide setting. Find it in the Settings tab of Manage branches in the Frontend. In a service, it appears on the Branches page. Only Owners and Admins can change it. Everyone else sees the current value. The setting is called Archie Reviewer reviews automatically. It controls whether Archie reviews a pull request when it is opened:
Archie never reviews on its own at any other time. After the first review, it reviews again only when someone asks.
The setting applies to the Frontend and to all services.
The Archie review checkbox in the Open pull request dialog follows this setting. It starts checked unless the setting is Never. You can check or clear it for each pull request.
Require Archie’s review
A protected branch can require Archie’s review before a pull request merges. Turn on Require Archie Reviewer in the protection rules of the branch. While Archie has not reviewed, or its review is out of date, Merge status shows messages such as Archie hasn’t reviewed yet and the merge is blocked.What a review costs and when it is charged
- A review needs enough available credits. Without them, the review is refused with “Couldn’t review: not enough credits.” and a Buy credits button.
- Before you request a review, a dialog explains that the review costs at least a number of credits, depending on the size of the pull request. Confirm with Confirm and charge.
- Requesting a review again is charged again.
- If Archie already reviewed the same commit, it does not review it again and nothing is charged.
- If Archie runs out of credits before it finishes, the review is partial. The notice reads Reviewed x of y files, and you can request the review again.
- Applying a suggestion is free.