Code review¶
Drape reviews your pull requests and comments on the bugs it finds. You turn it on per repository and choose how deep each repository's reviews go. Go to Code Review → Repositories to change these settings.
When Drape reviews¶
Once a repository has code review on, Drape reviews each pull request when it opens or is marked ready for review, and again on every push. Drafts and pull requests opened by bots are skipped by default.
Repository members and collaborators can ask for a review at any time by commenting on the pull request:
/drape reviewasks for a Review./drape deep-reviewasks for a Deep Review.
Review tier¶
The tier sets how deep a repository's reviews go unless someone asks for the other one.
| Tier | What it does |
|---|---|
| Review | A focused pass when a pull request opens and on each push. |
| Deep Review | A longer, more thorough pass, for code where a missed bug costs the most. |
When a member comments /drape deep-review on a pull request, later pushes to that pull request
get Deep Review too, until someone comments /drape review.
Each review costs credits: a base amount plus an amount for every 100 changed lines. Deep Review costs more than Review. The Code Review → Repositories page shows the current price of each tier, and Billing explains how credits work.
Comment inline¶
This setting decides which findings Drape posts as comments on the changed lines. Findings at or above the chosen severity are posted inline. Lower ones are listed, folded, in the review's summary comment, so they don't crowd the pull request.
| Setting | Posted inline |
|---|---|
| Low and above | Every finding |
| Medium and above | Medium, High, and Critical findings |
| High and above | High and Critical findings |
| Critical only | Critical findings |