Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/copilot/concepts/agents/code-review
What part(s) of the article would you like to see updated?
|
* The policy is **most restrictive**. {% data variables.copilot.copilot_code-review_short %} is only available in repositories where you explicitly enable the policy. |
In "Enabling code review for users without a license," the third policy characteristic implies a repository-level control that admins must enable per repository. No such control exists in repository settings, and no procedure for one is documented. The "How it works for users without a license" section of the same article describes the actual behavior: once the two organization policies are enabled, members without a license can request reviews across the organization's repositories. Verified in a Copilot Business organization — enabling the org sub-policy makes Copilot requestable on PRs in every repository, with no repository-level step.
If a repository-level control is planned, the docs should say where it lives; otherwise, the sentence should be removed. (Repository scoping is only documented for automatic code review via rulesets, which may be what this sentence intended to reference.)
Additional information
Enabling or disabling this sub-policy emails every member of the organization ("Your access to Copilot code review has been enabled/disabled"), so an enable-and-revert cycle caused by this wording produced two org-wide notification rounds (140+ members each) for us.
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/copilot/concepts/agents/code-review
What part(s) of the article would you like to see updated?
docs/content/copilot/concepts/agents/code-review.md
Line 68 in ecb3e3d
In "Enabling code review for users without a license," the third policy characteristic implies a repository-level control that admins must enable per repository. No such control exists in repository settings, and no procedure for one is documented. The "How it works for users without a license" section of the same article describes the actual behavior: once the two organization policies are enabled, members without a license can request reviews across the organization's repositories. Verified in a Copilot Business organization — enabling the org sub-policy makes Copilot requestable on PRs in every repository, with no repository-level step.
If a repository-level control is planned, the docs should say where it lives; otherwise, the sentence should be removed. (Repository scoping is only documented for automatic code review via rulesets, which may be what this sentence intended to reference.)
Additional information
Enabling or disabling this sub-policy emails every member of the organization ("Your access to Copilot code review has been enabled/disabled"), so an enable-and-revert cycle caused by this wording produced two org-wide notification rounds (140+ members each) for us.