Repository navigation
upload-sarif: git call failed. more times than necessary for a working directory without a git repository #3383
Description
codeql-action/src/git-utils.ts
Line 87 in f67ec12
https://github.com/check-spelling-sandbox/skipper/actions/runs/20649925837/job/59292941788
Run github/codeql-action/upload-sarif@7434149006143a4d75b82a2f411ef15b03ccc2d7
git call failed. Continuing with commit SHA from user input or environment. Error: The checkout path provided to the action does not appear to be a git repository.
Uploading code scanning results
Processing sarif files: ["cifuzz-sarif/results.sarif"]
Validating cifuzz-sarif/results.sarif
Adding fingerprints to SARIF file. See https:https://github.com/proxy/docs.github.com/en/enterprise-cloud@latest/code-security/code-scanning/integrating-with-code-scanning/sarif-support-for-code-scanning#providing-data-to-track-code-scanning-alerts-across-runs for more information.
(node:12002) [DEP0169] DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. CVEs are not issued for `url.parse()` vulnerabilities.
(Use `node --trace-deprecation ...` to show where the warning was created)
git call failed. Continuing with commit SHA from user input or environment. Error: The checkout path provided to the action does not appear to be a git repository.
git call failed. Continuing with commit SHA from user input or environment. Error: The checkout path provided to the action does not appear to be a git repository.
git call failed. Will calculate the base branch SHA on the server. Error: The checkout path provided to the action does not appear to be a git repository.
Uploading results
Successfully uploaded results
Waiting for processing to finish
git call failed. Continuing with commit SHA from user input or environment. Error: The checkout path provided to the action does not appear to be a git repository.Ideally, the action should be able to "quickly" determine that there isn't a repository checked out and not waste additional time running git commands.
Note that this flow (using google/clusterfuzzlite/actions/run_fuzzers and then ideally uploading sarif output) is a flow that people expect to be able to do (yes, Google is missing documentation for how to do it, but...).
Activity
mbg commentedon Jan 5, 2026
Hi @jsoref 👋🏻
Just to confirm, are you finding that these calls to
gitadd a meaningful overhead for you or are leading to any other problems? The workflow run you linked to seems to show thatupload-sarifcompleted in 8s and thegitcalls seem to account for only a few ms each.I agree that it would be ideal if we didn't make any unnecessary calls to external programs like
git, but it's probably not worth addressing this for a relatively rare use-case if there's no functional/meaningful time impact.jsoref commentedon Jan 5, 2026
You're right that the clock time isn't particularly exciting. It also isn't my workflow. My code I don't use this library anymore.
Error messages should add something. Having repeated error messages for the same problem doesn't do that, it makes it harder for people to deal with things.