Skip to main content

Gitmoot v0.2.0-beta.2

Gitmoot v0.2.0-beta.2 stabilizes the parallel PR lifecycle work from the 0.2.0 beta line and publishes the validated issue #50 fixes.

Highlights​

  • Parallel gitmoot task run flows now create task-owned worktrees reliably under checkout-lock contention.
  • The daemon now reconciles stale/current-head review state and can complete post-delivery advancement retries automatically.
  • Merge-conflict comments now explain the concrete repair path: resolve manually or queue a Gitmoot-owned implement/fix job, then rerun review/merge.
  • Local planning files now live under ignored /GOALS/, and release artifacts under /dist/ are ignored.

Validation​

  • GOTOOLCHAIN=local /tmp/go1.26.4/bin/go test ./internal/workflow ./internal/daemon ./internal/cli -timeout 420s
  • git diff --check
  • Real disposable GitHub smoke with four parallel tasks:
    • four task worktrees auto-created
    • four daemon-consumed implementation jobs
    • four PRs opened and merged by Gitmoot
    • task worktrees removed after merge
    • remote task branches deleted after merge
    • disposable repo deleted after validation

Known Beta Limits​

  • gitmoot daemon start --repo owner/repo still expects to be run from a checkout whose origin matches the target repo. Issue #202 tracks making --repo resolve the registered checkout directly or return a clearer actionable error.
  • Release assets currently include gitmoot_linux_amd64 only.