GitHub adds API controls for Copilot code review settings
GitHub has expanded API management of Copilot code review settings across enterprise, organisation and repository levels. The update also makes review overview comments more compact and adds clearer attribution for Copilot output.
By JetherVerse News

GitHub announced Copilot code review updates on November 6, including management of review settings through REST and GraphQL APIs. The changes cover enterprise policy, organisation configuration and repository settings, with access depending on the administrator's role.
The APIs also expose explicit attribution for Copilot reviews and comments, plus review effort and reported sources when available. Enterprise and organisation settings endpoints do not support GitHub Apps or fine-grained personal access tokens; repository settings endpoints support both with appropriate Administration permissions. GitHub also redesigned Copilot's review overview comment. The updates cover Copilot Pro, Pro+, Max, Business and Enterprise plans.
JetherVerse perspective: businesses adopting automated review should first decide what the review is meant to contribute. A useful policy could ask for help finding defects, checking a particular convention or drawing attention to an unfamiliar change. Writing down that purpose makes it easier to judge whether a growing stream of comments is improving the work or merely adding another queue for developers to clear.
A practical evaluation should include a small sample of real changes and a named human reviewer. Ask the reviewer which comments led to a correction, which needed clarification and which were irrelevant. Keep those judgments alongside the change so that a future policy adjustment has a clear reason behind it.
Administration deserves the same attention as the review itself. Record who owns the settings, how the team would notice an unexpected change and who can restore the agreed configuration. For an agency working across several client projects, those responsibilities should be understandable without relying on one person's memory of a settings page.
Our suggested next step is to document one review workflow from request to final decision. Include who can change the process and what evidence is needed before a release. The value of a configurable assistant is the ability to fit a clear working practice. The team still needs to define that practice and check that the tool is helping it deliver dependable changes.
Image: GitHub's official Copilot code review illustration.
Source: GitHub
Get the news in your inbox
The tech stories that matter from JetherVerse News, with the source on every one.

