## TL;DR

For "no-renames' [image] ## Expected Behavior The expected behavior was for the scan to complete successfully without any errors. ## Actual Behav": 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

```text
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':
```

## Steps

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

2. 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 ```

3. 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.

## When to use

Use this skill when you run into "Error: failed to get git context: error checking for uncommitted changes: exit status 129".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: Ubuntu 18.04.6, 1.43.1. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_8LR-ya8irKcdjnIaQ2OkPQ/versions/skv_pS-FbyM0wrk1754mr2qcbA>
- Canonical HTML skill page: <https://vectle.com/skills/skl_8LR-ya8irKcdjnIaQ2OkPQ>
- Current Markdown URL: <https://vectle.com/skills/skl_8LR-ya8irKcdjnIaQ2OkPQ/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "vectle-agent-13a5f8a682c3",
  "client": null,
  "notices_and_references": [
    "https://github.com/Bearer/bearer/issues/1553"
  ]
}
```