Settings
Codzee works well out of the box. These settings let you tune it to how your team works. Everyone can see them; admins can change them.
How Codzee reviews
- How sure Codzee must be before it comments. The default is 75%. Raise it for fewer, surer comments; lower it to see more.
- What to comment on. Bugs, security and performance are on. Style and nitpicks are off, and you can turn them on.
- Size labels on each pull request. On by default.
- Pause reviews for the whole organization.
- What fails the check. See The Codzee check.
Each repository can have its own settings too (how sure Codzee must be, pausing, size labels and the number of reviewers). Open the repository in the dashboard and click the settings icon. Anything you don't change there follows the organization.
Who reviews each PR
On a pull request's first review, Codzee asks the people who know the code best to review it, and says why in the summary. In Settings → Routing you choose how many reviewers to add (2 by default, 0 to turn it off) and who to leave out.
How Codzee chooses:
- Who wrote or recently changed the lines in the pull request, and who works in those folders.
- Who has reviewed this code before. Recent work counts more than old work.
- Who's already busy. People with many open review requests are less likely to be picked.
- Only people who can write to the repository. Bots are never picked.
When a review finds something serious, Codzee adds a second reviewer.
Notifications
Each person chooses their own in Settings → Your notifications:
- You're asked to review: in the dashboard, or as a Slack message.
- Weekly digest: an email every Monday with what happened last week. On by default; turn it off any time.
An admin connects Slack once, in Settings → Integrations. Codzee matches people by the email on their GitHub account. On Codzee Cloud, admins also get an email when the organization has used 80% and 100% of its reviewed pull requests for the month.
Repositories
Settings → Repositories lists the repositories Codzee can review. To add or remove one, change the list in GitHub. A repository you remove keeps its history in the dashboard, and an admin can delete that history for good from this page.
Who can change what
| Role | What they can do |
|---|---|
| Admin | Everything: settings, review rules, team, billing, reports and security scans. GitHub organization owners are always admins. |
| Member | Sees the dashboard, their Inbox and every setting, but can't change them. |
| Billing admin | Pays the bill and sees reports. Doesn't take a paid seat unless they open pull requests. |
Admins invite people and change roles in Team.
Can't find what you need? Email support@codzee.io and we'll help.