1
0
mirror of synced 2025-12-19 18:10:59 -05:00
Files
docs/content/code-security/code-scanning/troubleshooting-code-scanning/unclear-what-triggered-a-workflow-run.md
2023-09-21 19:29:29 -07:00

1.5 KiB

title, shortTitle, intro, allowTitleToDifferFromFilename, versions
title shortTitle intro allowTitleToDifferFromFilename versions
Unclear what triggered a workflow run Unclear what triggered a workflow If you don't know what triggered an analysis, {% ifversion code-scanning-tool-status-page %} investigate the {% data variables.code-scanning.tool_status_page %} or {% endif %}look at the log for the last scan. true
feature
code-scanning-without-workflow

{% data reusables.code-scanning.beta %}

The {% data variables.code-scanning.tool_status_page %} shows you how well {% data variables.product.prodname_code_scanning %} tools are working for a repository, when files in the repository were first scanned and most recently scanned, and when scans are scheduled. For integrated tools like {% data variables.product.prodname_codeql %}, you can also see more detailed information, including a percentage of files scanned and specific error messages. For more information about the {% data variables.code-scanning.tool_status_page %}, see "AUTOTITLE."

You can also view the logging output from {% data variables.product.prodname_code_scanning %} runs using {% data variables.product.prodname_actions %} ({% data variables.product.prodname_codeql %} or third-party). For more information, see "AUTOTITLE."