---
title: "Get a Proofline report into GitHub code scanning | Proofline Help"
description: "Generating a SARIF file in the review step and uploading it to GitHub are separate workflow steps. Check each step when GitHub has no code scanning results for the run."
url: https://proofline.sh/help/ci-sarif-upload/
---

[Help center](/help/)

# Get a Proofline report into GitHub code scanning

Generating a SARIF file in the review step and uploading it to GitHub are separate workflow steps. Check each step when GitHub has no code scanning results for the run.

## Locate the file before checking upload permissions

In the review step, check the filename passed to `--sarif` and whether the CLI found a pull-request review for the head. When no review appears before the deadline, there is no review file to upload. If export was refused, read the reason in that step.

In the upload step, confirm that `sarif_file` points to the same path and that the job has `security-events: write`. A review can produce a file even when its exit code is nonzero. The [GitHub Actions example](/docs/ci/) runs the upload after the review step whenever the file exists. Open the upload step’s log to check whether GitHub accepted it.

## Related guides

-   [Read a review](/help/read-review/)
-   [Read Proofline results in CI](/help/read-proofline-results-in-ci/)
