メモ
GitHub Code Quality is currently in パブリック プレビュー and subject to change. During パブリック プレビュー, Code Quality will not be billed, although Code Quality scans will consume GitHub Actions minutes.
Prerequisites
- GitHub Actions must be enabled because Code Quality uses actions to run each CodeQL analysis.
- To get the full benefit of the feature, your repository should include one of the languages supported for quality analysis by CodeQL. See Supported languages.
Enabling Code Quality for a repository
-
GitHub で、リポジトリのメイン ページに移動します。
-
リポジトリ名の下にある [Settings] をクリックします。 [設定] タブが表示されない場合は、 [] ドロップダウン メニューを選び、 [設定] をクリックします。
![タブを示すリポジトリ ヘッダーのスクリーンショット。 [設定] タブが濃いオレンジ色の枠線で強調表示されています。](/assets/cb-28260/images/help/repository/repo-actions-settings.png)
-
In the sidebar, under "Security", click Code quality to display the "Code quality" page.
-
Click Enable code quality.
メモ
If Enable code quality is missing from this view, your enterprise owner has disabled the use of Code Security and Code Quality for your organization. See Allowing use of GitHub Code Quality in your enterprise.
-
Review the information on the Code quality page:
- Languages: If you want to disable CodeQL analysis for any of the languages, clear the associated check box.
- Runner type: If you want to use a different runner, choose Labeled runner and define the Runner label. See GitHub ホステッド ランナーの使用 and セルフホストランナーとのラベルの利用.
-
Click Save changes to save your configuration for Code Quality.
ヒント
If your organization has configured caching of private registries, these will be available for code quality analysis to use to resolve dependencies. See セキュリティ機能にプライベート レジストリへのアクセスを許可する.
Next steps
- Learn about the code quality backlog for your repository. See Interpreting the code quality results for your repository.
- Find and fix code quality issues before they reach your default branch. See Fixing code quality findings before merging your pull request.