With new organization runner controls, Copilot content exclusion support, and the removal of the character limit on repository custom instructions, Copilot code review is now easier to tailor to your needs within your repository and organization.
With the release of Copilot code review’s agentic architecture, we announced that Copilot code review is powered by GitHub Actions. By default, Copilot code review runs on the standard GitHub-hosted runner, but teams can configure self-hosted or large runners for more control over the runner type. To support ease of setup of custom runners, Copilot code review’s runner type can now be configured at the organization-level, meaning that one configuration can apply to all repositories within the organization.
Organization admins can now:
To set this up, navigate to your organization, then go to Copilot -> Runner type -> Runner type configuration. Your configuration will apply to both Copilot code review and Copilot cloud agent if both are enabled.
Copilot code review now respects repository, organization, and enterprise-level Copilot content exclusion settings, so you can prevent Copilot from utilizing specified files or directories during its review. Repository administrators can configure excluded paths in repository settings using path-based rules.
This gives you control over which repository content is available to Copilot code review, helping you align reviews with your team, organization, or enterprise’s boundaries, or prevent Copilot from utilizing context that isn’t relevant to the review.
For more information, check out our docs about configuring content exclusions for Copilot.
Previously, Copilot code review would stop reading copilot-instructions.md and *.instructions.md files located under the .github directory once the file reached 4000 characters in size. That limit has now been removed, allowing additional customization and flexibility in your custom instructions.
Join the discussion within GitHub Community.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。