Support Zizmor SARIF uploads from private repositories

Open
#390 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@trask is already working on this.

Since Sep 17, 2026.

Assessment

This issue has not been assessed yet.

Description

The reusable Zizmor workflow cannot upload SARIF results from private repositories. github/codeql-action/upload-sarif reads workflow-run metadata during processing, which requires actions: read in both the caller and reusable workflow.

Adding actions: read to the existing reusable job changes its permission contract. Callers that upgrade without granting the new permission can be rejected before the job runs, even though public repositories do not need it.

Add a backward-compatible private-repository path, such as a separate reusable workflow or an explicit opt-in that leaves existing public callers unchanged.

Acceptance criteria:

  • A private repository caller can complete the Zizmor audit and SARIF upload.
  • Existing public caller configuration continues to work unchanged.
  • Consumer documentation shows the private-repository configuration.
  • The behavior is verified from a private repository.
Dominant language
JavaScript
Stars
7
Forks
23
Avg merge
15h 46m
Merged PRs (30d)
41

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-telemetry/shared-workflows

All issues in open-telemetry/shared-workflows

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.