Skip to content

chore: gitignore .claude/ agent worktree scratch directories - #1502

Draft
seonghobae wants to merge 3 commits into
mainfrom
chore/gitignore-claude-worktrees
Draft

chore: gitignore .claude/ agent worktree scratch directories#1502
seonghobae wants to merge 3 commits into
mainfrom
chore/gitignore-claude-worktrees

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

Summary

Background coding-agent sessions dispatched with isolated worktree mode create .claude/worktrees/<agent-id>/ inside this repo's own working tree (a nested git checkout used for an in-flight background agent). That directory is local tool-managed scratch state, not repository content — it was showing up as untracked in git status and tripping a local pre-stop hygiene check.

Changes

  • Add .claude/ to .gitignore.

Verification

  • Purely additive .gitignore entry; no code paths touched. git status in an affected checkout no longer lists the worktree directory as untracked.

Generated by Claude Code

Background agents dispatched with isolated worktree mode create
.claude/worktrees/<agent-id>/ inside this repo's own working tree. That
directory is local tool-managed scratch state (a nested git checkout for
an in-flight background agent), not repository content, and was showing
up as untracked in `git status` for anyone working in this checkout.
@coderabbitai

coderabbitai Bot commented Aug 31, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

… gate test

assert_opencode_review_uses_codegraph_and_contextual_orchestrator's awk
range `/^  required-workflow-bootstrap:$/,/^[^ ]/` never terminates in this
file, since job keys are always 2-space indented and no truly-unindented
line exists anywhere in the jobs: section. This silently pulled every job
after required-workflow-bootstrap into the "must have no if:" check,
tripping on an unrelated, legitimate if: condition on a later job's step
and failing this required check on every open .github-repo PR.
required-workflow-bootstrap itself has always had zero if: conditions --
only the test's own job-scoping was broken. Replace the range with an
explicit state machine that starts at the bootstrap job header and stops
at the next 2-space-indented job key.

Verified: `bash scripts/ci/test_strix_quick_gate.sh` now passes (previously
failed with exactly the false-positive record_failure this fix removes);
full suite (2125 passed, 1 skipped, 21 subtests) and `git diff --check`
clean.

Copy link
Copy Markdown
Contributor Author

opencode-review failed on this head after exhausting its 90-minute active-dispatch-and-poll window with no opencode-agent verdict — the same structural class of failure as #1500/#1503 (see docs/product-technical-gap-baseline.md's 2026-08-31 "opencode-review structural deadlock" entry), not caused by this PR's own trivial .gitignore change. This PR has no unresolved review threads, so it isn't the specific unresolved-thread gate I root-caused there; likely the same runner-queue-contention or another decide()-path cause I haven't fully traced for #1503 either. Triggering the one allowed re-run now. This PR is also behind main — will update the branch separately since that's unrelated to this check's own failure.


Generated by Claude Code

seonghobae pushed a commit that referenced this pull request Aug 31, 2026
noema-review (#1415), opencode-review (#1500/#1502/#1503), and strix
(#1503) all independently timed out today with the identical shape: a
required check dispatches a repository_dispatch run against main, then
polls for evidence; the dispatched run sat queued (never picked up by a
runner) for well over an hour, so the poller gave up and reported
failure. Documented as an infrastructure capacity question, not a
per-PR code defect.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KPmJErfkcHer4UVEgrQxUX

Copy link
Copy Markdown
Contributor Author

opencode-review failed again on c5a2c8f5 (job 99553711209) — this is not this PR's diff (a trivial .gitignore addition). The job log shows the actual mechanism clearly this time: #1497's active-dispatch-and-poll verdict step ran the full 180 × 30s = 90 minutes (16:53:42 → 18:24:18) waiting for an opencode-agent APPROVED/CHANGES_REQUESTED review on this exact head, and none ever posted. This is a sharper, confirmed root cause than my earlier "runner-queue-starvation" standing-down comment on this same PR — the dispatched run isn't queued-and-never-scheduled here, it's the OpenCode review agent itself not completing/posting within its own 90-minute budget. Already tracked as a separate, open question (see #1494's closing comment and docs/product-technical-gap-baseline.md's congestion entries); no fix attempted here, still out of scope for this PR's own diff.


Generated by Claude Code

@seonghobae

Copy link
Copy Markdown
Contributor Author

Contextual-Orchestrator와 관계한 것들을 같이 손보든 어쩌든 해결하세요. Bypass merge 필요하면 가능 (chicken and eggs 상황이라면) + NVIDIA NIM 만 쓰는 건 허용하지 않아요. Contextual-Orchestrator를 쓰세요. Timeout은 적어도 3시간으로 잡으세요. 120초 같은 건 당황스럽군요. Opencode와 Noema 는 Coderabbitai 및 Devin 수준으로 실제로 리뷰를 하게 하시오. Strix도 보안 리뷰를 꼼꼼하게 하도록 하시오. 특히 보안 리뷰는 전체 코드로 수행하는 것입니다. Contextual-Orchestrator는 실시간으로 빠르면서 능력이 좋은 모델에 요청을 보내어 시간을 당기시오.

@seonghobae seonghobae added maintenance type: maintenance Maintenance, build, dependency, or operational upkeep priority: medium Normal-priority or P2 work labels Sep 7, 2026 — with ChatGPT Codex Connector
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance priority: medium Normal-priority or P2 work type: maintenance Maintenance, build, dependency, or operational upkeep

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants