Skip to content

handoff-spawn: detect Graphite from real tracking, never hang on gt track - #34

Merged
simoncrypta merged 1 commit into
masterfrom
graphite-detect
Nov 7, 2026
Merged

simoncrypta merged 1 commit into
masterfrom
graphite-detect

Conversation

@simoncrypta

Copy link
Copy Markdown
Owner

Part of v0.11.0, stacked on #33.

Why: running any gt command in a non-Graphite repo (bercail) left .graphite_* files behind, so handoff-spawn took the repo for a Graphite repo, and gt track --force hung until the spawn aborted.

What:

  • Graphite detection now uses the [graphite] override in config.toml, or whether the base branch is actually tracked by gt, not just whether .graphite_* files exist.
  • gt track is bounded by a timeout, no longer uses --force, and a failure doesn't abort the spawn.
  • Adds new cases to tests/handoff_spawn_test.sh, and updates the docs and config.toml.example.

Proof: all 28 tests/*.sh pass (58 handoff assertions). Not tried on macOS.

…rack

Only treat a repo as Graphite when [graphite] in config.toml says so or the base branch is actually tracked by gt, not just because .graphite_* files exist. Bound gt track with a timeout, drop --force, and keep the spawn going if tracking fails. Adds handoff_spawn_test.sh cases and updates the docs and config example.
@simoncrypta
simoncrypta changed the base branch from review-pr-tui to master November 7, 2026 05:10
@simoncrypta
simoncrypta merged commit 955af07 into master Nov 7, 2026
2 of 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