jesseduffield / jesseduffield/lazygit
Corrupted file paths
- Vorherrschende Sprache
- Go
- Sterne
- 82.4k
- Forks
- 3k
- Ø Merge
- 2 T. 18 Std.
- Gemergte PRs (30 T.)
- 19
Beschreibung
**Describe the bug**
File paths often get "corrupted" (usually after a large change, such as big checkout of many files)
**To Reproduce**
Not a single way I can reproduce consistently.
Last example was "edit" on a previous commit. Git checkout of a hundred of files (via git cli)
file paths are corrupt (safe-ea/src instead of geaosafe-ea/src)
**Expected behavior**
no corruption
**Screenshots**

**Version info:**
3.11 geosafe-ea ⟩ lazygit --version
commit=aa331e52b8a0e5da03c59ee6b9bd1d2a9073618c, build date=2025-06-07T02:32:24Z, build source=binaryRelease, vers
ion=0.52.0, os=linux, arch=amd64, git version=2.43.0
3.11 geosafe-ea ⟩ git --version
git version 2.43.0
**Additional context**
I hit this bug randomly for a year (since I start using lazygit). I upgrade often, same random bug.
**Note:** please try updating to the latest version or [manually building](https://github.com/jesseduffield/lazygit/#manual) the latest `master` to see if the issue still occurs.
Logs when I try to type space on corrupt file
[development.log](https://github.com/user-attachments/files/20687968/development.log)
Beitragsleitfaden
Rechercherichtung
Start by reproducing the reported sequence: edit a previous commit, then use the Git CLI to check out many files and inspect the resulting paths in lazygit. Review the attached development.log, compare the displayed path with the expected path, and verify that the corruption and related typing error no longer occur.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- git, go
- Bereich
- cli
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100