Kevin Loftis
5af63f755d
* fix: use --no-optional-locks for background git status calls Prevent index.lock contention by adding --no-optional-locks to all git status --porcelain calls. This is the same approach VSCode uses in its built-in git extension (GIT_OPTIONAL_LOCKS=0). The status-line component polls git status every ~1s to show staged/unstaged/untracked counts. Without --no-optional-locks, each call acquires index.lock for an opportunistic index refresh, which blocks concurrent git operations (pull, rebase, commit) run by the user or by omp's own tool execution. The git-status documentation explicitly recommends this: 'Scripts running status in the background should consider using git --no-optional-locks status' References: - git docs: https://git-scm.com/docs/git-status (BACKGROUND REFRESH) - git commit adding the flag: https://github.com/git/git/commit/27344d6 - VSCode's fix: GIT_OPTIONAL_LOCKS=0 in extensions/git/src/git.ts:2716 - Claude Code same issue: https://github.com/anthropics/claude-code/issues/11005 - GitExtensions same issue: https://github.com/gitextensions/gitextensions/issues/5066 - VSCode issue #31069: https://github.com/microsoft/vscode/issues/31069 * style: fix biome formatting for long lines in worktree.ts