Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

codeql/upload-sarif@v2 or @main can't integrate on actions

Open
#1,806 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, go
Domain
ci-cd, security

Research direction

The workflow YAML is the entry point; start by reproducing Snyk's snyk.sarif generation and the github/codeql-action/upload-sarif@v2 step, then inspect the workflow's integration permissions and repository context. Done means the workflow uploads snyk.sarif successfully and the code-scanning result is visible without the reported resource-access error.

Written by the indexing model from the issue text.

Description

image

The error is Error: codeql/upload-sarif action failed: Resource not accessible by integration
My case is try to integrate snyk for sast on my golang code, and then upload sarif file to github to look any vulnerabilities summary.

My workflow actions yaml files:

jobs:
  unit_test:
    runs-on: ubuntu-latest
    steps:
    - name: Checkout Repo
      uses: actions/checkout@v3

    - name: Set up Go
      uses: actions/setup-go@v4
      with:
        go-version: '1.20'
        
    - name: Unit test
      continue-on-error: false 
      run: go test ./...
      
    - name: SAST Test
      uses: snyk/actions/golang@master
      continue-on-error: true 
      env:
        SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}
      with:
        command: code test
        args: --sarif-file-output=snyk.sarif
    
    - name: Upload SAST Test Result
      uses: github/codeql-action/upload-sarif@v2
      with:
        sarif_file: snyk.sarif
Dominant language
TypeScript
Stars
1.6k
Forks
493
Avg merge
1d 13h
Merged PRs (30d)
44

Contributor guide

Open the contributing guide

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 github/codeql-action

All issues in github/codeql-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.