Publicamos atualizações frequentes em nossa documentação, e a tradução desta página ainda pode estar em andamento. Para obter as informações mais recentes, acesse a documentação em inglês. Se houver problemas com a tradução desta página, entre em contato conosco.

Enabling code scanning for a repository

You can enable Varredura de código for your project's repository.

People with write permissions to a repository can enable Varredura de código for the repository.

Neste artigo

Did this doc help you?

Nota: Varredura de código está atualmente em versão beta e sujeito a alterações. To request access to the beta, join the waitlist.

Options for enabling Varredura de código

You decide how you generate Varredura de código alerts, and which tools you use, at a repository level. GitHub provides fully integrated support for CodeQL analysis, and also supports analysis using third-party tools. For more information, see "About CodeQL."

Type of analysis Options for generating alerts
CodeQL Using GitHub Actions (see "Enabling Varredura de código using actions") or using the CodeQL runner in a third-party continuous integration (CI) system (see "Running code scanning in your CI system").
Third‑party Using GitHub Actions (see "Enabling Varredura de código using actions") or generated externally and uploaded to GitHub (see "Uploading a SARIF file to GitHub").

Enabling Varredura de código using actions

Using actions to run Varredura de código will use minutes. For more information, see "About billing for GitHub Actions."

  1. No GitHub, navegue até a página principal do repositório.
  2. Under your repository name, click Security.
    Guia de segurança
  3. To the right of "Code scanning", click Set up code scanning.
    "Set up code scanning" button to the right of "Code scanning" in the Security Overview
  4. Under "Get started with code scanning", click Set up this workflow on the CodeQL Analysis workflow or on a third-party workflow.
    "Set up this workflow" button under "Get started with code scanning" heading
  5. Optionally, to customize how Varredura de código scans your code, edit the workflow. For more information, see "Configuring Varredura de código."
  6. Use the Start commit drop-down, and type a commit message.
    Start commit
  7. Choose whether you'd like to commit directly to the default branch, or create a new branch and start a pull request.
    Choose where to commit
  8. Click Commit new file or Propose new file.

After you commit the workflow file or create a pull request, Varredura de código will analyze your code according to the frequency you specified in your workflow file. If you created a pull request, Varredura de código 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.

Next steps

After you enable Varredura de código, you can monitor analysis, view results, and further customize how you scan your code.

Did this doc help you?