注意：代码扫描 目前处于测试阶段，可能会更改。 有关参加公测的更多信息，请在此注册。
注：站点管理员必须为 your GitHub Enterprise Server instance 启用 代码扫描，然后您才可使用此功能。 如果要使用 GitHub Actions 扫描代码，站点管理员还必须启用 GitHub Actions 并设置所需的基础结构。 更多信息请参阅“为设备配置 代码扫描”。
在仓库级别决定如何生成 代码扫描 警报，以及使用哪些工具。 GitHub Enterprise Server 对 CodeQL 分析提供完全集成的支持，还支持使用第三方工具进行分析。 更多信息请参阅“关于 CodeQL”。
|CodeQL||使用 GitHub Actions（请参阅“使用操作启用 代码扫描”）或在第三方持续集成 (CI) 系统中使用 CodeQL runner（请参阅“在 CI 系统中运行代码扫描”）。|
|第三方||使用 GitHub Actions（请参阅“使用操作启用 代码扫描”）或者外部生成并上传到 GitHub Enterprise Server（请参阅“上传 SARIF 文件到 GitHub”）。|
在 GitHub Enterprise Server 上，导航到仓库的主页面。
To the right of "Code scanning", click Set up code scanning.
Under "Get started with code scanning", click Set up this workflow on the CodeQL 分析工作流程 or on a third-party workflow.
Optionally, to customize how 代码扫描 scans your code, edit the workflow. For more information, see "Configuring 代码扫描."
Generally you can commit the CodeQL 分析工作流程 without making any changes to it. However, many of the third-party workflows require additional configuration, so read the comments in the workflow before committing.
使用 Start commit（开始提交）下拉菜单，并键入提交消息。
单击 Commit new file（提交新文件）或 Propose new file（提议新文件）。
In the default CodeQL 分析工作流程, 代码扫描 is configured to analyze your code each time you either push a change to the default branch or any protected branches, or raise a pull request against the default branch. As a result, 代码扫描 will now commence.
You decide how you generate 代码扫描 alerts, and which tools you use, at a repository level. GitHub Enterprise Server provides fully integrated support for CodeQL analysis, and also supports analysis using third-party tools. For more information, see "About CodeQL."
After you enable 代码扫描, you can monitor analysis, view results, and further customize how you scan your code.
Click the entry for the 代码扫描 workflow.
Click the job name on the left. For example, Analyze (LANGUAGE).
Review the logging output from the actions in this workflow as they run.
Once all jobs are complete, you can view the details of any 代码扫描 alerts that were identified. For more information, see "Managing 代码扫描 alerts for your repository."
Note: If you raised a pull request to add the 代码扫描 workflow to the repository, alerts from that pull request aren't displayed directly on the 代码扫描 page until the pull request is merged. If any alerts were found you can view these, before the pull request is merged, by clicking the n alerts found link in the banner on the 代码扫描 page.
Each 代码扫描 workflow you enable to run on pull requests always has at least two entries listed in the checks section of a pull request. There is one entry for each of the analysis jobs in the workflow, and a final one for the results of the analysis.
The names of the 代码扫描 analysis checks take the form: "TOOL NAME / JOB NAME (TRIGGER)." For example, for CodeQL, analysis of C++ code has the entry "CodeQL / Analyze (cpp) (pull_request)." You can click Details on a 代码扫描 analysis entry to see logging data. This allows you to debug a problem if the analysis job failed. For example, for 代码扫描 analysis of compiled languages, this can happen if the action can't build the code.
When the 代码扫描 jobs complete, GitHub works out whether any alerts were added by the pull request and adds the "代码扫描 results / TOOL NAME" entry to the list of checks. After 代码扫描 has been performed at least once, you can click Details to view the results of the analysis. If you used a pull request to add 代码扫描 to the repository, you will initially see a "Missing analysis" message when you click Details on the "代码扫描 results / TOOL NAME" check.
After 代码扫描 has analyzed the code in a pull request, it needs to compare the analysis of the topic branch (the branch you used to create the pull request) with the analysis of the base branch (the branch into which you want to merge the pull request). This allows 代码扫描 to compute which alerts are newly introduced by the pull request, which alerts were already present in the base branch, and whether any existing alerts are fixed by the changes in the pull request. Initially, if you use a pull request to add 代码扫描 to a repository, the base branch has not yet been analyzed, so it's not possible to compute these details. In this case, when you click through from the results check on the pull request you will see the "Missing analysis for base commit SHA-HASH" message.
There are other situations where there may be no analysis for the latest commit to the base branch for a pull request. These include:
The pull request has been raised against a branch other than the default branch, and this branch hasn't been analyzed.
To check whether a branch has been scanned, go to the 代码扫描 page, click the Branch drop-down and select the relevant branch.
The latest commit on the base branch for the pull request is currently being analyzed and analysis is not yet available.
Wait a few minutes and then push a change to the pull request to retrigger 代码扫描.
An error occurred while analyzing the latest commit on the base branch and analysis for that commit isn't available.
Merge a trivial change into the base branch to trigger 代码扫描 on this latest commit, then push a change to the pull request to retrigger 代码扫描.
After enabling 代码扫描, and allowing its actions to complete, you can:
- View all of the 代码扫描 alerts generated for this repository. 更多信息请参阅“管理仓库的 代码扫描 警报”。
- View any alerts generated for a pull request submitted after you enabled 代码扫描. For more information, see "Triaging 代码扫描 alerts in pull requests."
- Set up notifications for completed runs. 更多信息请参阅“配置通知”。
- Investigate any problems that occur with the initial setup of CodeQL 代码扫描. For more information, see "Troubleshooting the CodeQL workflow."
- Customize how 代码扫描 scans the code in your repository. 更多信息请参阅“配置 代码扫描。”