Error: failed to get git context: error checking for uncommitted changes: exit status 129

Error: failed to get git context: error checking for uncommitted changes: exit status 129

What was going on Issue Bearer/bearer#1553 (closed, 9 comments): ## Description & Reproduction When running the SAST tool, the following error occurs: error: failed to get git context: error checking for uncommitted changes: exit status 129 -- git output -- error: unknown option no-renames' [image] ## Expected Behavior The expected behavior was for the scan to complete successfully without any errors. ## Actual Behavior the scan failed to complete successfully ## Your Environment - Operating System and version: Ubuntu 18.04.6 LTS - Output of 'bearer version': bearer version: 1.43.1, build: e267aa91d68a9e3e70890b03ded971b12c30d95f

The fix [Morgbn (commenter)]: The "failed to get git context" error comes from git rev-parse --abbrev-ref origin/HEAD failing, usually because origin/HEAD is not set in your local clone. Fix: run git remote set-head origin -a, then rerun the scan.

In gh:Bearer/bearer#1553 the issue was: Issue Bearer/bearer#1553 (closed, 9 comments): ## Description & Reproduction When running the SAST tool, the following error occurs: error: failed to get git context: error checking for uncommitted changes: exit status 129 -- git output -- error: unknown option no-renames' [image] ## Expected Behavior The expected behavior was for the scan to complete successfully without any errors. ## Actual Behavior the scan failed to complete successfully ## Your Environment - Operating System and version: Ubuntu 18.04.6 LTS - Output of 'bearer version': bearer version: 1.43.1, build: e267aa91d68a9e3e70890b03ded971b12c30d95f `` The verified answer: [Morgbn (commenter)]: The "failed to get git context" error comes from git rev-parse --abbrev-ref origin/HEAD failing, usually because origin/HEAD is not set in your local clone. Fix: run git remote set-head origin -a, then rerun the scan. Source: https://github.com/Bearer/bearer/issues/1553