revert(dogfood): clean up ci-status.sh comment + re-prove downstream-impact by don-petry · Pull Request #854 · combsmith/.github-private

don-petry · 2026-06-21T02:09:53Z

Two birds

Cleanup: removes the throwaway Ring-0 dogfood comment that merged via test(dogfood): exercise downstream-impact pass on @pr-review/next #850 into the shared lib scripts/lib/ci-status.sh. The diff restores the file to its pre-dogfood state exactly.
Re-prove: this revert is itself a comment-only change to ci-status.sh — a surface_source of .github/workflows/pr-review.yml — so it doubles as the retry dogfood for the downstream-impact pass (Cross-repo impact-aware review annotations: proactive downstream-breakage detection in the pr-review pipeline #748 / pr-review: enable the downstream-impact pass (default-on + kill switch) #815), now live on @pr-review/next.

Why a retry was needed

#850 merged before its verdict rendered: the review job kept getting cancelled by dev-lead's auto-rebase churn (main was very active). This PR is labeled dev-lead:hands-off so dev-lead skips it and the review / review job can run to completion uninterrupted.

Expected verdict annotation

compute_downstream_impact (deterministic, unit-tested) predicts the agent's verdict should carry a Downstream impact section naming:

Surface: .github/workflows/pr-review.yml
Consumers (5): petry-projects/.github-private, petry-projects/ContentTwin, petry-projects/bmad-bgreat-suite, petry-projects/google-app-scripts, petry-projects/markets

The dogfood passes when that section appears in the self-host agent's review. Safe to merge on its own merits (it's a clean revert).

https://claude.ai/code/session_014djuNDBa3GASVDLQPXXg9L

Generated by Claude Code

…tream-impact Removes the throwaway 'Ring-0 dogfood' comment that merged via #850 into the shared lib scripts/lib/ci-status.sh. This revert is itself a comment-only change to that same surface_source, so it doubles as the retry dogfood: the self-host pr-review agent (v1.7.0 via @pr-review/next) should now post a verdict carrying a 'Downstream impact' section naming the consumers that pin .github/workflows/pr-review.yml (.github-private, ContentTwin, bmad-bgreat-suite, google-app-scripts, markets). Labeled dev-lead:hands-off so dev-lead doesn't rebase/cancel the review job mid-run (the churn that prevented #850's verdict from completing). https://claude.ai/code/session_014djuNDBa3GASVDLQPXXg9L

chatgpt-codex-connector · 2026-06-21T02:09:57Z

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

coderabbitai · 2026-06-21T02:10:03Z

Warning

Review limit reached

@don-petry, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 34 minutes and 40 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d40b463c-f896-40f4-97a2-04c89fc92510

📥 Commits

Reviewing files that changed from the base of the PR and between bf04bea and c605a4d.

📒 Files selected for processing (1)

scripts/lib/ci-status.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch claude/revert-dogfood-and-reprove

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 and usage tips.}

gemini-code-assist

Code Review

This pull request removes a temporary dogfooding comment from the scripts/lib/ci-status.sh script. There are no review comments, and I have no feedback to provide.

sonarqubecloud · 2026-06-21T02:10:38Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

don-petry · 2026-06-21T02:10:44Z

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

donpetry-bot · 2026-06-21T02:11:06Z

Advisory bots were rate-limited; auto-approval is withheld until they recover. pr-review-sweep will re-review this PR after 2026-06-21T03:11:06Z.

donpetry-bot

Automated review — APPROVED ✓

Risk: LOW
Reviewed commit: c605a4d50d09254bd74ae53612eae2e77bc55309
Review mode: triage-approved (single reviewer)

Summary

Comment-only revert: removes the 3-line 'Ring-0 dogfood' comment block from scripts/lib/ci-status.sh, restoring the file to its pre-#850 state exactly. Zero additions, three deletions, one file. No executable code, control flow, or interface changes.

Linked issue analysis

No closing issue is referenced (closingIssuesReferences is empty), which is appropriate for a cleanup revert. The PR description cites #850 (the dogfood it reverts) and #748/#815 (the downstream-impact initiative) as context only. The stated goal — undo a throwaway comment — is fully satisfied by the diff.

Findings

No issues. The change deletes only comment lines, so there is no runtime or downstream behavioral impact: ci-status.sh is sourced by the pr-review workflow, but a comment removal cannot alter compute_ci_status behavior. Secret scan: not applicable — the diff has no added/modified content to scan (deletions only); the gitleaks CI check passed independently. Triage-tier low-risk assessment confirmed.

CI status

All functional checks green: CodeQL (actions/python), gitleaks secret scan, shellcheck/ShellCheck, bats, unit/unit-tests, SonarCloud (Quality Gate passed), AgentShield, holdout-guard, and CI lint all SUCCESS. The CANCELLED dev-lead/dispatch and dev-lead/ci-relay jobs are expected — the PR carries the dev-lead:hands-off label so dev-lead intentionally skips it. review/review and dependabot are SKIPPED (trigger jobs). Advisory bots (CodeRabbit, Codex) were rate-limited; gemini-code-assist reviewed with no feedback. mergeStateStatus is BLOCKED only on REVIEW_REQUIRED, not on any failing check.

Reviewed automatically by the PR-review agent (single-reviewer mode: fable 5). Reply if you need a human review.

…tream-impact (#854) Removes the throwaway 'Ring-0 dogfood' comment that merged via #850 into the shared lib scripts/lib/ci-status.sh. This revert is itself a comment-only change to that same surface_source, so it doubles as the retry dogfood: the self-host pr-review agent (v1.7.0 via @pr-review/next) should now post a verdict carrying a 'Downstream impact' section naming the consumers that pin .github/workflows/pr-review.yml (.github-private, ContentTwin, bmad-bgreat-suite, google-app-scripts, markets). Labeled dev-lead:hands-off so dev-lead doesn't rebase/cancel the review job mid-run (the churn that prevented #850's verdict from completing). https://claude.ai/code/session_014djuNDBa3GASVDLQPXXg9L Co-authored-by: Claude <noreply@anthropic.com>

don-petry requested a review from a team as a code owner June 21, 2026 02:09

don-petry added the dev-lead:hands-off Exclude from dev-lead agent automation label Jun 21, 2026 — with Claude

gemini-code-assist Bot reviewed Jun 21, 2026

View reviewed changes

don-petry enabled auto-merge (squash) June 21, 2026 02:10

donpetry-bot approved these changes Jun 21, 2026

View reviewed changes

don-petry merged commit ded84ce into main Jun 21, 2026
42 of 44 checks passed

don-petry deleted the claude/revert-dogfood-and-reprove branch June 21, 2026 02:15

github-actions Bot mentioned this pull request Jun 23, 2026

petry-projects — workflow failures detected 2026-06-23 #912

Closed

github-actions Bot mentioned this pull request Jun 25, 2026

petry-projects — workflow failures detected 2026-06-25 #930

Closed

github-actions Bot mentioned this pull request Jun 2, 2026

petry-projects — workflow failures detected 2026-06-02 #419

Closed

github-actions Bot mentioned this pull request Aug 30, 2026

petry-projects — workflow failures detected 2026-08-30 #1586

Closed

Navigation Menu

Repository navigation

revert(dogfood): clean up ci-status.sh comment + re-prove downstream-impact - #854

revert(dogfood): clean up ci-status.sh comment + re-prove downstream-impact#854
don-petry merged 1 commit into
mainfrom
claude/revert-dogfood-and-reprove

don-petry commented Jun 21, 2026

Uh oh!

chatgpt-codex-connector Bot commented Jun 21, 2026

Uh oh!

coderabbitai Bot commented Jun 21, 2026

Review limit reached

Uh oh!

gemini-code-assist Bot left a comment

Uh oh!

sonarqubecloud Bot commented Jun 21, 2026

Uh oh!

don-petry commented Jun 21, 2026

Uh oh!

donpetry-bot commented Jun 21, 2026

Uh oh!

donpetry-bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

don-petry commented Jun 21, 2026

Two birds

Why a retry was needed

Expected verdict annotation

Uh oh!

chatgpt-codex-connector Bot commented Jun 21, 2026

Uh oh!

coderabbitai Bot commented Jun 21, 2026

Review limit reached

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

sonarqubecloud Bot commented Jun 21, 2026

Quality Gate passed

Uh oh!

don-petry commented Jun 21, 2026

Dev-Lead — review-changes (no-changes)

Uh oh!

donpetry-bot commented Jun 21, 2026

Uh oh!

donpetry-bot left a comment

Choose a reason for hiding this comment

Automated review — APPROVED ✓

Summary

Linked issue analysis

Findings

CI status

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants