Skip to content

ci: Lighthouse CI + skip claude-review on forks#24

Merged
rdmueller merged 2 commits into
LLM-Coding:mainfrom
raifdmueller:ci/lighthouse
Apr 15, 2026
Merged

ci: Lighthouse CI + skip claude-review on forks#24
rdmueller merged 2 commits into
LLM-Coding:mainfrom
raifdmueller:ci/lighthouse

Conversation

@raifdmueller
Copy link
Copy Markdown
Contributor

Summary

Two CI improvements bundled (see #23):

1. Lighthouse CI with budgets

New workflow `lighthouse.yml` runs on every PR against `main`:

  • Build → serve static `dist/` → `lhci autorun` (3 runs, median)
  • Desktop preset, simulated throttling
  • Upload to `temporary-public-storage` (no LHCI server needed)

Budgets (established from local baseline measurement):

Category Minimum Baseline Level
Performance 0.80 0.89 error
Accessibility 0.85 0.89 error
Best Practices 0.90 1.00 error
SEO 0.95 1.00 error

Web Vitals (warnings only, not blocking):

  • LCP ≤ 2500ms, TBT ≤ 300ms, CLS ≤ 0.1

Known issues surfaced by the baseline (tracked as follow-ups):

  • Accessibility at 89: color-contrast, label, label-content-name-mismatch audits flag real issues
  • Performance headroom exists in `asciidoctor.js` bundle size — lazy-loading would improve LCP/TBT

2. Skip claude-code-review on fork PRs

The `CLAUDE_CODE_OAUTH_TOKEN` secret is not available in fork-PR contexts (GitHub security model), so `claude-code-review.yml` always failed on PRs from `raifdmueller/vibe-coding-risk-radar`. Added:

```yaml
if: github.event.pull_request.head.repo.full_name == github.repository
```

CodeRabbit already provides AI review on fork PRs, and `@claude` mentions (via `claude.yml`) still work on demand. Org-internal PRs are unaffected.

Test plan

  • Local Lighthouse run passes all assertions (3 runs, median 89/89/100/100)
  • Build still passes
  • Verify Lighthouse CI runs successfully in GitHub Actions (first PR run will establish CI-side baseline)
  • Verify claude-code-review is skipped (should show as skipped, not failed, on this PR)

Closes #23

🤖 Generated with Claude Code

raifdmueller and others added 2 commits April 15, 2026 15:20
The CLAUDE_CODE_OAUTH_TOKEN secret is not available in fork-PR
contexts (GitHub security model), so the action always fails
on PRs from raifdmueller/vibe-coding-risk-radar.

For fork PRs, CodeRabbit already provides AI review automatically,
and @claude mentions (via claude.yml, event-triggered) still work
on demand.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Lighthouse CI runs on every PR against main. Budgets (category-level
scores, error-blocking unless noted):

  Performance:   >= 0.80 (baseline 0.89, desktop preset)
  Accessibility: >= 0.85 (baseline 0.89, color-contrast/labels flagged)
  Best Practices:>= 0.90 (baseline 1.00)
  SEO:           >= 0.95 (baseline 1.00)

Web Vitals as warnings (monitoring only, not blocking):
  LCP <= 2500ms, TBT <= 300ms, CLS <= 0.1

Setup:
- @lhci/cli, http-server, wait-on as devDependencies
- lighthouserc.json at repo root with desktop preset
- .github/workflows/lighthouse.yml: build → serve → lhci autorun
- Upload to temporary-public-storage (no LHCI server required)
- .lighthouseci/ gitignored

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

coderabbitai Bot commented Apr 15, 2026

Warning

Rate limit exceeded

@raifdmueller has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 22 minutes and 5 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 22 minutes and 5 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b1f9e4b0-9dd7-400c-a941-8f23a9d6a86c

📥 Commits

Reviewing files that changed from the base of the PR and between a4f2cf0 and b210c9a.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (5)
  • .github/workflows/claude-code-review.yml
  • .github/workflows/lighthouse.yml
  • .gitignore
  • lighthouserc.json
  • package.json
✨ 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 and usage tips.

@rdmueller rdmueller merged commit 4830505 into LLM-Coding:main Apr 15, 2026
6 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.

CI: Lighthouse CI mit Performance/A11y/SEO Budgets

2 participants