docs(code-review): note that bot authors occupy billed seats - #82
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
|
I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".
|
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5c0ecbe4cd
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| pull request is reviewed occupies a seat like any other developer, including | ||
| through [auto-assignment](/code-review/people#auto-assign-seats-on-pr). | ||
| Exclude bots with [`exclude.authors`](/code-review/config#exclude-scans) or | ||
| the org-wide author filter, or remove their seats from **People**. |
There was a problem hiding this comment.
Clarify that removing a bot seat does not prevent reassignment
When auto-assignment remains enabled, deleting a bot's People seat is not an alternative to excluding it: the next eligible bot PR can assign it again under the auto-assignment rule in code-review/people.mdx:21, and this page already states that a mid-period deletion does not reduce that period's seat count (code-review/billing.mdx:21). Presenting removal alongside the filters as a way to address bot billing can therefore leave customers with renewed assignments and charges; describe it as removing only the current assignment and direct users to an author filter to prevent future assignments.
Useful? React with 👍 / 👎.
| bots out of review and billing, list their usernames in | ||
| [`exclude.authors`](/code-review/config#exclude-scans) or the org-wide author | ||
| filter — excluded authors are skipped before a seat is assigned. You can also |
There was a problem hiding this comment.
Note that repository author filters override the org filter
This does not reliably keep bots out of review and billing for repositories that set exclude.authors themselves: the configuration hierarchy uses the repository category when present (code-review/config.mdx:21-24), and an empty value explicitly clears the organization default (code-review/config.mdx:96). Organizations with per-repository author settings can therefore add the bot to the org-wide filter and still have it auto-assigned in those repositories; instruct them to add the exclusion to each overriding repository or verify that no override exists.
Useful? React with 👍 / 👎.
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Summary
Adds a short
<Note>in two places clarifying that eligible bot authors (e.g.dependabot[bot],renovate[bot]) occupy billed Code Review seats like any other developer — surfaced by a customer who was surprised thatdependabot[bot]andhacktron-app[bot]were auto-assigned seats and billed.code-review/people.mdx— under Auto-assign seats on PR: auto-assignment applies to eligible bot authors; excluded authors are skipped before a seat is assigned; bots can be kept out viaexclude.authors/ the org-wide author filter, and seats can be removed from People.code-review/billing.mdx— under the seat-count intro: a reviewed bot PR occupies a seat, with the same exclusion/removal pointers.No behavior change — docs only.
Link to Devin session: https://app.devin.ai/sessions/24a7ebe530c34fd6b9c72a76977d6c6a
Open in Devin Desktop: https://app.devin.ai/desktop/session/24a7ebe530c34fd6b9c72a76977d6c6a?variant=devin
Requested by: @zeyu2001