Skip to content

CLAUDE.md: monitor CI after every push#25

Open
jnasbyupgrade wants to merge 1 commit into
Postgres-Extensions:masterfrom
jnasbyupgrade:ci-monitor-doc
Open

CLAUDE.md: monitor CI after every push#25
jnasbyupgrade wants to merge 1 commit into
Postgres-Extensions:masterfrom
jnasbyupgrade:ci-monitor-doc

Conversation

@jnasbyupgrade

Copy link
Copy Markdown
Contributor

Broadens the existing GitHub CI monitoring instruction in CLAUDE.md from "a branch with an open PR" to every push:

  • Use gh pr checks <pr> --watch when the branch has an open PR.
  • Otherwise (branch with no PR yet, or a push to master) use gh run watch for the pushed commit.
  • Notes that docs-only pushes (**.md/**.asc) are excluded from CI by paths-ignore, so there's nothing to watch for those.

Docs-only change; CI is skipped via paths-ignore.

🤖 Generated with Claude Code

Broaden the GitHub CI instruction to cover every push, including a branch
without a PR yet and pushes to master (use `gh run watch` for the commit when
there is no PR). Note that docs-only pushes are excluded from CI via
paths-ignore, so there is nothing to watch for those.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 12, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 15 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: ad5f3ba1-f1ed-40b4-852f-65cdb5dd1d8c

📥 Commits

Reviewing files that changed from the base of the PR and between 18ae203 and d4aebba.

📒 Files selected for processing (1)
  • CLAUDE.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

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