Skip to content

feat(autosync): RILL_AUTOSYNC_START=0 turns off hook-start only - #108

Merged
tarr1124 merged 1 commit into
mainfrom
feat/autosync-start-skip
Oct 20, 2026
Merged

tarr1124 merged 1 commit into
mainfrom
feat/autosync-start-skip

Conversation

@tarr1124

Copy link
Copy Markdown
Contributor

Why

A GUI that resumes a past Claude Code conversation only to show it waited for a full rill autosync run (fetch, rebase, push) in the SessionStart hook before the conversation appeared: 1.5–2.5 s with nothing to push, up to the 60 s lock wait while another run holds the lock (for example the GUI's own one-minute sync). That GUI keeps the vault in step on its own timer, so the wait buys nothing there.

RILL_AUTOSYNC=0 is not usable for this: it also turns off hook-stop, and a process's environment cannot change after spawn, so the conversation's later turns would never be pushed by the hook.

What

  • rill autosync hook-start does nothing when RILL_AUTOSYNC_START=0. hook-stop, run, check are unaffected.
  • Help text and the header comment describe the variable.
  • test/cli/test-autosync.sh: hook-start with the variable commits and pushes nothing; hook-stop with the variable still pushes. 55/55 pass.

Codex review: no findings.

🤖 Generated with Claude Code

A caller that opens a Claude Code conversation just to show it (the Rill
GUI resuming a past conversation without a prompt) waited for a full
fetch, rebase and push before the conversation appeared: 1.5-2.5 s with
nothing to push, up to the 60 s lock wait while another run holds the
lock. The GUI already keeps the vault in step on its own timer, so that
wait buys nothing there. RILL_AUTOSYNC=0 cannot be used: it also turns
off hook-stop, and a process's environment cannot change after spawn.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tarr1124
tarr1124 merged commit 33f1738 into main Oct 20, 2026
4 checks passed
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.

1 participant