Viewing code scanning logs from GitHub Actions

View the output from a code scanning analysis in GitHub Actions.

Wer kann dieses Feature verwenden?

Benutzer*innen mit Lesezugriff

Hinweis

Der Websiteadministrator muss code scanning aktivieren, damit du dieses Feature verwenden kannst. Wenn du GitHub Actions zum Überprüfen deines Codes verwenden möchtest, muss der Websiteadministrator auch GitHub Actions aktivieren und die erforderliche Infrastruktur einrichten. Weitere Informationen finden Sie unter Konfigurieren der Codeüberprüfung für Ihre Anwendung.

After configuring code scanning using default setup or a custom GitHub Actions workflow, you can watch the output of the actions as they run. For information about logs for other code scanning setups, see Code scanning logs.

  1. Klicke unter dem Repositorynamen auf Actions.

    Screenshot: Registerkarten für das Repository „github/docs“. Die Registerkarte „Aktionen“ ist mit einem orangefarbenen Rahmen hervorgehoben.

    You'll see a list that includes an entry for running the code scanning workflow. The text of the entry is the title you gave your commit message.

    Screenshot of the "All workflows" page. In the list of workflow runs is a run labeled "Create .github/workflows/codeql.yml."

  2. Click the entry for the code scanning workflow.

    Hinweis

    If you are looking for the CodeQL workflow run triggered by enabling default setup, the text of the entry is "CodeQL."

  3. Click the job name on the left. For example, Analyze (LANGUAGE).

    Screenshot of the log output for the "Analyze (go)" job. In the left sidebar, under the "Jobs" heading, "Analyze (go)" is listed.

  4. Review the logging output from the actions in this workflow as they run.

  5. Optionally, to see more detail about the commit that triggered the workflow run, click the short commit hash. The short commit hash is 7 lowercase characters immediately following the commit author's username.

  6. Once all jobs are complete, you can view the details of any code scanning alerts that were identified. For more information, see Bewerten von Warnungen der Codeüberprüfung für das Repository.

Further reading

If you're looking for diagnostic information about whether code scanning accessed any private registries, see Viewing code scanning logs from GitHub Actions.