Skip to content

ci(lighthouse): lower performance threshold to 70 for CI runner variance#28

Merged
tehw0lf merged 1 commit into
mainfrom
fix/lighthouse-performance-threshold
Jun 27, 2026
Merged

ci(lighthouse): lower performance threshold to 70 for CI runner variance#28
tehw0lf merged 1 commit into
mainfrom
fix/lighthouse-performance-threshold

Conversation

@tehw0lf

@tehw0lf tehw0lf commented Jun 27, 2026

Copy link
Copy Markdown
Owner

Summary

  • CI performance scores vary wildly (55-94%) vs local scores (99%) due to GitHub Actions runner load
  • Lower min_performance from 95 to 70 as a realistic safety net that catches real regressions
  • Other thresholds (a11y, best-practices, seo) unchanged

@coderabbitai

coderabbitai Bot commented Jun 27, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

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

To continue reviewing without waiting, enable usage-based billing in the billing tab.

⌛ 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 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 42ab8166-58b1-4b1f-8675-60c8cfbaf228

📥 Commits

Reviewing files that changed from the base of the PR and between 1769476 and f0d8d9c.

📒 Files selected for processing (1)
  • .github/workflows/lighthouse-scan.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/lighthouse-performance-threshold

Comment @coderabbitai help to get the list of available commands.

@tehw0lf tehw0lf force-pushed the fix/lighthouse-performance-threshold branch from 93b50ea to f0d8d9c Compare June 27, 2026 15:28
@tehw0lf tehw0lf enabled auto-merge (squash) June 27, 2026 15:34
@tehw0lf tehw0lf merged commit 088a332 into main Jun 27, 2026
20 checks passed
@tehw0lf tehw0lf deleted the fix/lighthouse-performance-threshold branch June 27, 2026 15:34
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