Prerequisites
- If your organization belongs to an enterprise, an enterprise owner must enable Code Quality for your organization. See 엔터프라이즈에서 GitHub Code Quality를 사용하는 것을 허용하기.
- Your organization must have repositories with Code Quality enabled. See GitHub Code Quality 사용.
Viewing code quality insights for your organization
- On GitHub, navigate to the main page of your organization. For example, from https://github.com/settings/organizations.
- 조직 이름 아래에서 탭을 Security and quality 클릭합니다.
- In the "Insights" section of the sidebar, click Code quality.
참고
What you see on the dashboard depends on your access:
- Organization owners see data for every repository that has Code Quality enabled.
- All other organization members see data only for repositories where they can view Code Quality findings (the repository-level pages), up to a maximum of 3,000 repositories.
Interpreting the score distribution chart
The score distribution chart provides a visual overview of the code health of your organization. Each bubble represents a collection of repositories with the same maintainability and reliability scores.
- The position of each bubble demonstrates the overall health of those repositories. Higher bubbles represent higher maintainability scores, while bubbles further to the right represent higher reliability scores.
- The color and border pattern of a bubble indicate the severity of the lower score for those repositories. For example, a bubble with a "Poor" score in either category will always be red with a dashed border.
- The size of each bubble represents the number of repositories with that particular score combination.
To view the maintainability score, reliability score, and number of repositories represented by a particular bubble, hover over the bubble.
Exploring the repository table
Below the bubble chart, there is a table that lists all repositories in your organization. Here, you can view code quality findings, along with more detailed information about those findings.
You can sort the repository table in ascending or descending order for any column by clicking the column header.
Investigating low-scoring repositories
- To filter the dashboard data for the lowest-performing repositories, on the score distribution chart, click the bubble with the lowest combined scores.
- Scroll down to the repository table. By default, the table is sorted from most to least recent repository scan, helping you prioritize current quality issues.
- Optionally, to prioritize repositories with the highest number of CodeQL findings, click Standard Findings twice.
- To view the repository-level dashboard for a specific repository, click the repository's name.
Next steps
To understand the code health information available on the repository-level dashboard, see 리포지토리에 대한 코드 품질 결과 해석.