5839299a49
* New Crowdin translations by Github Action * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Ran script/fix-translation-errors.js * Reverted translated files with parsing and rendering errors * Update script to skip checked in list of files to reset for broken translations * Temporarily enable all langauges to check CI status * Need better performance for more languages * Revert "Update script to skip checked in list of files to reset for broken translations" This reverts commit f88f01a0f790fcd9fba5fc79937edd923263b6c5. * Revert changes used to test CI passes when all languages are enabled Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
6.1 KiB
title, intro, product, permissions, miniTocMaxHeadingLevel, redirect_from, versions, topics, shortTitle
| title | intro | product | permissions | miniTocMaxHeadingLevel | redirect_from | versions | topics | shortTitle | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Viewing code scanning logs | You can view the output generated during {% data variables.product.prodname_code_scanning %} analysis in {% data variables.product.product_location %}. | {% data reusables.gated-features.code-scanning %} | If you have write permissions to a repository, you can view the {% data variables.product.prodname_code_scanning %} logs for that repository. | 4 |
|
|
|
View code scanning logs |
{% data reusables.code-scanning.beta %} {% data reusables.code-scanning.enterprise-enable-code-scanning-actions %}
About your {% data variables.product.prodname_code_scanning %} setup
You can use a variety of tools to set up {% data variables.product.prodname_code_scanning %} in your repository. For more information, see "Setting up {% data variables.product.prodname_code_scanning %} for a repository."
{% ifversion fpt or ghes > 3.1 or ghae-next or ghec %} The log and diagnostic information available to you depends on the method you use for {% data variables.product.prodname_code_scanning %} in your repository. You can check the type of {% data variables.product.prodname_code_scanning %} you're using in the Security tab of your repository, by using the Tool drop-down menu in the alert list. For more information, see "Managing {% data variables.product.prodname_code_scanning %} alerts for your repository."
About analysis and diagnostic information
You can see analysis and diagnostic information for {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_codeql %} analysis on {% data variables.product.prodname_dotcom %}.
Analysis information is shown for the most recent analysis in a header at the top of the list of alerts. For more information, see "Managing code scanning alerts for your repository."
Diagnostic information is displayed in the Action workflow logs and consists of summary metrics and extractor diagnostics. For information about accessing {% data variables.product.prodname_code_scanning %} logs on {% data variables.product.prodname_dotcom %}, see "Viewing the logging output from {% data variables.product.prodname_code_scanning %}" below.
If you're using the {% data variables.product.prodname_codeql_cli %} outside {% data variables.product.prodname_dotcom %}, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file you upload to {% data variables.product.prodname_dotcom %} with the {% data variables.product.prodname_code_scanning %} results.
For information about the {% data variables.product.prodname_codeql_cli %}, see "Configuring {% data variables.product.prodname_codeql_cli %} in your CI system."
About summary metrics
{% data reusables.code-scanning.summary-metrics %}
About {% data variables.product.prodname_codeql %} source code extraction diagnostics
{% data reusables.code-scanning.extractor-diagnostics %}
{% endif %}
Дальнейшие шаги
This section applies to {% data variables.product.prodname_code_scanning %} run using {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} or third-party).
After setting up {% data variables.product.prodname_code_scanning %} for your repository, you can watch the output of the actions as they run.
{% data reusables.repositories.actions-tab %}
You'll see a list that includes an entry for running the {% data variables.product.prodname_code_scanning %} workflow. The text of the entry is the title you gave your commit message.
-
Click the entry for the {% data variables.product.prodname_code_scanning %} 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.
-
After a scan completes, you can view alerts from a completed scan. For more information, see "Managing {% data variables.product.prodname_code_scanning %} alerts for your repository."
{% note %}
After you commit the workflow file or create a pull request, {% data variables.product.prodname_code_scanning %} will analyze your code according to the frequency you specified in your workflow file. If you created a pull request, {% data variables.product.prodname_code_scanning %} will only analyze the code on the pull request's topic branch until you merge the pull request into the default branch of the repository.
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
{% else %}
{% endif %}
{% endnote %}