Stefan Haller c1cd500fa7 Retry lock errors reported only through the command's error ... Have isRetryableError also inspect the returned error, not just the captured output. Streamed commands (amend, commit, and other operations run through the gpg helper) don't capture output, so their index.lock failures were slipping past the retry loop and surfacing to the user as a hard "Git command failed". Now they retry like every other command. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-07-15 10:08:44 +02:00
..
direnv	Offer direnv .envrc approval from inside lazygit	2026-06-04 09:05:01 +02:00
git_commands	Show renamed files in the custom patch builder	2026-07-04 13:05:09 +02:00
git_config	Enable errorlint linter, and fix warnings	2025-06-30 18:30:11 +02:00
hosting_service	Optimize regex compilations	2026-05-10 15:28:14 +02:00
models	Show renamed files in the custom patch builder	2026-07-04 13:05:09 +02:00
oscommands	Use ConPTY on Windows for pty-backed command execution	2026-07-03 18:47:15 +02:00
patch	Show renamed files in the custom patch builder	2026-07-04 13:05:09 +02:00
testdata	Support opening lazygit in a submodule	2019-05-12 17:59:49 +10:00
git.go	Show renamed files in the custom patch builder	2026-07-04 13:05:09 +02:00
git_cmd_obj_builder.go	Suppress optional locks by default again, except foreground refresh	2026-07-02 16:05:08 +02:00
git_cmd_obj_builder_test.go	Suppress optional locks by default again, except foreground refresh	2026-07-02 16:05:08 +02:00
git_cmd_obj_runner.go	Retry lock errors reported only through the command's error	2026-07-15 10:08:44 +02:00
git_cmd_obj_runner_test.go	Retry lock errors reported only through the command's error	2026-07-15 10:08:44 +02:00