Skip to main content
Skip to content

Viewing repository insights

Use Repository insights to understand how your team acts on Copilot code review feedback and identify opportunities to improve review practices.

누가 이 기능을 사용할 수 있나요?

People with read access to the repository.

When deciding how to improve your team's review process, use Repository insights to see where Copilot code review coverage is missing and which feedback developers act on. It brings review outcomes together with pull request activity, so you can consider them alongside throughput and merge times.

Use this overview to choose where to investigate unaddressed feedback, expand review coverage, or adjust review practices. These signals support those decisions, but do not prove that code is defect-free or that Copilot caused an improvement.

Prerequisites

Repository insights is available for organization-owned repositories. You need read access to the repository.

The Copilot code review section appears only when the organization has enabled both the Copilot usage metrics policy and the Copilot code review policy. The Pull requests section is visible to anyone who can view the page.

For information about enabling these policies, see 조직의 GitHub Copilot 대한 정책 및 기능 관리.

Accessing Repository insights

  1. GitHub에서 리포지토리의 기본 페이지로 이동합니다.

  2. 리포지토리 이름 아래에서 인사이트를 클릭합니다.

    리포지토리의 기본 페이지 스크린샷. 수평 탐색 모음에서 그래프 아이콘과 "Insights" 레이블이 있는 탭이 주황색 윤곽선으로 표시됩니다.

  3. On the Repository insights page, review the Pull requests section for activity and merge-time context, then the Copilot code review section for feedback outcomes.

The weekly reporting period covers seven calendar days ending on the latest fully published day. Check the dates displayed on the page. If the latest data is older than expected, the page will indicate that data is delayed.

If you see "Waiting on your data", allow a few days for data to become available. This state does not mean the repository had no activity. Monthly address-rate trends have a separate reporting period and can have less history.

For metric definitions, reporting limits, and guidance on choosing follow-up actions, see Repository insights metrics.