Skip to content

fix: use --no-optional-locks for background git operations#186

Merged
marcus merged 1 commit intomarcus:mainfrom
borisvu:main
Feb 19, 2026
Merged

fix: use --no-optional-locks for background git operations#186
marcus merged 1 commit intomarcus:mainfrom
borisvu:main

Conversation

@borisvu
Copy link
Contributor

@borisvu borisvu commented Feb 18, 2026

Prevents index.lock conflicts when the file watcher triggers git status refreshes while write operations (stage, commit, checkout) are in progress.
All read-only git commands now use --no-optional-locks (git 2.15+), the standard approach for background monitoring tools.
Fixes #185

Prevents index.lock conflicts when the file watcher triggers git status
refreshes while write operations (stage, commit, checkout) are in progress.
All read-only git commands now use --no-optional-locks (git 2.15+), the
standard approach for background monitoring tools.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@marcus marcus mentioned this pull request Feb 19, 2026
@marcus marcus merged commit f25cc1c into marcus:main Feb 19, 2026
@marcus
Copy link
Owner

marcus commented Feb 19, 2026

Merged — thanks for the clean fix, @borisvu! The --no-optional-locks approach is the right call. 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Sidecar locks git

2 participants