Skip to content

check-pr on a plan PR doesn't seed its checkout - #119

Merged
hhff merged 2 commits into
mainfrom
plan-check-noseed
Nov 6, 2026
Merged

hhff merged 2 commits into
mainfrom
plan-check-noseed

Conversation

@hhff

@hhff hhff commented Nov 6, 2026

Copy link
Copy Markdown
Member

What

  • devteam.mjs: detachedWorktree takes { seed }. check-pr's plan path (validate --strict at the head) uses seed: false, so it copies no worktree_files and runs no worktree_setup. Merge's gate worktrees and goal measure readings still seed, because they run the project's commands.
  • Test: check-pr on a plan PR passes with worktree_setup set to a failing command and worktree_files naming a missing file.

Why

Since #100 and #108, the plan check's throwaway worktree was seeded like a worker's. In CI there's no toolchain and no untracked files, so every plan PR's check-pr failed. Stacks hit it: plan PR #428 got "worktree_setup failed" because bundle install had no Ruby on the runner, so every Stacks plan PR was blocked. The check only reads the plan and the log.

Migration

None.

🤖 Generated with Claude Code

hhff and others added 2 commits November 5, 2026 22:22
check-pr validates a plan PR's head in a detached worktree. Since sibling
repos (#108) that worktree was seeded like a worker's: worktree_files copied
and worktree_setup run. A CI runner has neither the project's toolchain nor
its untracked files, so every plan PR's check-pr failed in CI (Stacks:
"worktree_setup failed", bundle install with no Ruby). It only reads the plan
and the log: the checkout is no longer seeded.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s apply as on main)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hhff

hhff commented Nov 6, 2026

Copy link
Copy Markdown
Member Author

Merging for v0.20.2 (upstream loop). Main + #119 + #120 passed the full suite locally on Node 24.14.1 (129/129). CI 18/20/22/24 is green at this head, with current main merged in.

@hhff
hhff merged commit bdcc37d into main Nov 6, 2026
7 of 8 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