Skip to content

Prevent status reads from refreshing the Git index - #229

Merged
LuisPalacios merged 1 commit into
mainfrom
fix/171-status-no-optional-locks
Nov 14, 2026
Merged

LuisPalacios merged 1 commit into
mainfrom
fix/171-status-no-optional-locks

Conversation

@LuisPalacios

Copy link
Copy Markdown
Owner

Closes #171

What changed

  • Disable optional Git locks for summary and detailed status reads.
  • Verify unchanged index bytes and timestamps, preserved existing locks, and accurate modified/untracked results with real Git fixtures.
  • Update the architecture and test inventory in English and Spanish.

Test plan

  • Regression fails before the fix and passes afterward; ordinary status confirms the fixture can refresh the index.
  • Rebased onto Write credentials atomically and audit permissions #226; focused tests, vet, full health, Wails build and version smoke.
  • Interactive repository-details smoke and remote platform verification.

Interactive smoke testing remains required before merge.

Disable optional locks for summary and detailed status reads. Verify unchanged index contents and timestamps with real Git, including an existing lock and an ordinary-status control.

Closes #171
@LuisPalacios
LuisPalacios force-pushed the fix/171-status-no-optional-locks branch from e0e8b98 to 8f25446 Compare November 14, 2026 09:52
@LuisPalacios
LuisPalacios merged commit 9b95f4b into main Nov 14, 2026
3 checks passed
@LuisPalacios
LuisPalacios deleted the fix/171-status-no-optional-locks branch November 14, 2026 09:56
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.

[Phase 2] --no-optional-locks on every background status read

1 participant