Repository navigation
release: v3.11.0 — read-only sync for pull-only clones - #295
Merged
Merged
Conversation
git config found-issues.readonly true (or FOUND_ISSUES_READONLY=1) makes every sync in that clone a dry run: no closures, demotions, wake-ups or archive, so a pull-only clone never gets an uncommitted ledger edit that blocks its next git pull --ff-only. FOUND_ISSUES_READONLY=0 overrides the key for one command. doctor lists the setting. Closes ledger lib/sync.sh:770 (operator decision 2026-10-29). Also logs the slow serial test suite (tests/autofix-sweep.bats, decided: parallelize after this release). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MVx3HWniZnrXYfPiCo5Lrs
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MVx3HWniZnrXYfPiCo5Lrs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
git config found-issues.readonly true(orFOUND_ISSUES_READONLY=1) marks a clone read-only: every sync there (SessionStart, statusline autosync, post-merge hook, explicitfound-issues sync) becomes a dry run. It prints what it would close, demote, wake or archive, headedRead-only clone (found-issues.readonly) — nothing written., and writes nothing.FOUND_ISSUES_READONLY=0overrides the key for one command.found-issues doctorlists it under Hook opt-outs.Why
Ledger
lib/sync.sh:770, operator decision 2026-10-29: a pull-only clone (dougstation's agent-config) got uncommitted ledger edits from sync, and git refused its nextgit pull --ff-onlyeven when upstream had the byte-identical change. 3.10.10 removed one cause (commit-stale); this switch covers all of them.Evidence
tests/cli-sync-readonly.bats: 7/7 (red before the change except the two "normal writes" checks).1..2055, 2055 ok, 0 not ok, exit 0.Read-only clone (found-issues.readonly) — nothing written. Closed: 1 (0 PR + 0 commit + 1 tombstone).,git statusemptygit statusemptyFOUND_ISSUES_READONLY=0:Synced. Closed: 1 …, ledger modified! sync is read-only in this clone …Also logs the slow serial suite (
tests/autofix-sweep.bats, decided: parallelize after this release).🤖 Generated with Claude Code
https://claude.ai/code/session_01MVx3HWniZnrXYfPiCo5Lrs