We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sha
checkout_path
uses: github/codeql-action/upload-sarif@v3 with: sarif_file: sarif-results/fix-paths-cpp.sarif ref: refs/heads/main sha: a8e616ed369f7f74173a13c5489dbae89c3b12 checkout_path: /runner/_work/parent-repo/build
request: { method: 'PUT', url: 'https://github.com/api/v3/repos/PFO/OpenSIL/code-scanning/analysis', headers: { accept: 'application/vnd.github.v3+json', 'user-agent': 'CodeQL-Action/3.22.12 octokit-core.js/3.6.0 Node.js/20.18.0 (linux; x64)', authorization: 'token [REDACTED]', 'content-type': 'application/json; charset=utf-8' }, body: '{"commit_oid":"b0b0efb3f489d6c16d35gsfd4b388173h99e1049","ref":"refs/heads/main","analysis_key":".github/workflows/codeql-nightly.yml:codeql","analysis_name":"CodeQL- Nightly","sarif":"..."}'
From the output, we can see that it is not actually uploading with the commit_oid that we assigned in the sha input.
commit_oid
Looking at the src code of the upload-sarif action:
The text was updated successfully, but these errors were encountered:
Hi @acejarvis,
Thanks for your question. We are looking into it and will provide an update as soon as possible.
Sorry, something went wrong.
Could you share information on you use case of using sha option to help us understand if that use case is supported and we have a bug.
No branches or pull requests
From the output, we can see that it is not actually uploading with the
commit_oid
that we assigned in thesha
input.Looking at the src code of the upload-sarif action:
It is actually using the commit hash sha from the repo under the
checkout_path
, which completely ignores thesha
input in the action.The text was updated successfully, but these errors were encountered: