Skip to content

ci: make L1 lint lanes always-run (reliable branch-protection-required checks)#7

Merged
jeremylongshore merged 1 commit into
mainfrom
ci/l1-always-run
Jun 19, 2026
Merged

ci: make L1 lint lanes always-run (reliable branch-protection-required checks)#7
jeremylongshore merged 1 commit into
mainfrom
ci/l1-always-run

Conversation

@jeremylongshore

Copy link
Copy Markdown
Contributor

Drop the pull_request path filters from lint.yml + doc-quality.yml so the L1 lint lanes (yamllint, actionlint, markdownlint-cli2, lychee) run and report on every PR. A path-filtered required check is skipped on a non-matching PR and sits pending forever, blocking the PR. typos.yml already always-runs.

Beads: bd_000-projects-mjt1

Drop the pull_request path filters from lint.yml + doc-quality.yml so the
yamllint/actionlint/markdownlint/lychee checks run + report on every PR — a
path-filtered required check is skipped (never reports) on a non-matching PR
and blocks it forever. typos.yml already always-runs.
@gemini-code-assist

Copy link
Copy Markdown

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

More reviews will be available in 17 minutes and 57 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: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: de4f0c7e-c2db-47c8-8573-979d354d88fc

📥 Commits

Reviewing files that changed from the base of the PR and between cca23c6 and 5837bd6.

📒 Files selected for processing (2)
  • .github/workflows/doc-quality.yml
  • .github/workflows/lint.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/l1-always-run

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.

@jeremylongshore jeremylongshore merged commit 83e5742 into main Jun 19, 2026
10 checks passed
@jeremylongshore jeremylongshore deleted the ci/l1-always-run branch June 19, 2026 02:59
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