Skip to content

chore(gitignore): ignore .claude/arc-status.json* (BRO-1833 P1 — VPS partition)#1773

Merged
broomva merged 1 commit into
mainfrom
feature/bro-1833-arc-status-gitignore
Jul 9, 2026
Merged

chore(gitignore): ignore .claude/arc-status.json* (BRO-1833 P1 — VPS partition)#1773
broomva merged 1 commit into
mainfrom
feature/bro-1833-arc-status-gitignore

Conversation

@broomva

@broomva broomva commented Jul 9, 2026

Copy link
Copy Markdown
Owner

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's git add -A would 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-ignore now covers .json, .json.tmp, .json.tmp.<rand>, .json.new.

🤖 Generated with Claude Code

…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>
@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@broomva, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 53 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6a6f1052-0b6f-4107-8c27-05774468e464

📥 Commits

Reviewing files that changed from the base of the PR and between f4603c3 and 403de1f.

📒 Files selected for processing (1)
  • .gitignore
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feature/bro-1833-arc-status-gitignore

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.

@broomva broomva merged commit c35db1d into main Jul 9, 2026
17 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