chore(gitignore): ignore .claude/arc-status.json* (BRO-1833 P1 — VPS partition)#1773
Conversation
…partition) Mirror the workspace root .gitignore rule into core/life. This repo is the VPS Life-governor's $WORKDIR, so a dispatched arc's worktree here is governed by THIS .gitignore. Without the rule a VPS arc's `git add -A` would stage its runtime status file (.claude/arc-status.json) into the PR. Glob covers the file and any .tmp/temp variant. Companion to workspace PR #195 (BRO-1833 Phase P1). Found by the P20 cross-review gate (host-asymmetric gitignore, blocking B1). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 53 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Companion to workspace PR #195 — BRO-1833 Phase P1 (resumable governed arcs).
Why
The ticket-dispatch VPS Life-governor runs with
$WORKDIR=core/life, so the git worktrees it creates for dispatched arcs are linked worktrees of this repo — governed by this.gitignore. Phase P1 has arcs write a runtime status file at<WT>/.claude/arc-status.json(governor↔arc IPC, never a deliverable). Without a matching ignore here, a VPS arc'sgit add -Awould stage that file into its PR.Change
One line:
.claude/arc-status.json*(glob covers the file + any.tmp/mktemp temp variant). Mirrors the workspace root.gitignore.Provenance
Found by the P20 cross-model adversarial review of PR #195 as blocking finding B1 (host-asymmetric gitignore): the workspace-only ignore left the invariant "an arc's
git add .can never stage it" false on the VPS partition. Verified:git check-ignorenow covers.json,.json.tmp,.json.tmp.<rand>,.json.new.🤖 Generated with Claude Code