Skip to content

chore(ci): lower lighthouse performance threshold to 50#31

Merged
tehw0lf merged 2 commits into
mainfrom
chore/lighthouse-performance-threshold
Jun 30, 2026
Merged

chore(ci): lower lighthouse performance threshold to 50#31
tehw0lf merged 2 commits into
mainfrom
chore/lighthouse-performance-threshold

Conversation

@tehw0lf

@tehw0lf tehw0lf commented Jun 30, 2026

Copy link
Copy Markdown
Owner

Summary

  • Lowers min_performance from 70 to 50 in the weekly Lighthouse scan
  • CI runner scores are volatile and regularly dip below 70, causing false-positive failures
  • 50% is still a meaningful floor while eliminating noise from runner variance

Summary by CodeRabbit

  • Bug Fixes

    • Improved the app’s loading state structure for better semantic markup and accessibility.
  • Chores

    • Adjusted the weekly performance scan’s minimum threshold.

tehw0lf added 2 commits June 27, 2026 22:59
CI runner performance scores are volatile and regularly dip below 70.
Threshold lowered to 50 to avoid false-positive failures.
@coderabbitai

coderabbitai Bot commented Jun 30, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5c7278e3-d553-4ce1-9ff6-20cf241df9ba

📥 Commits

Reviewing files that changed from the base of the PR and between af02c76 and 46c1b99.

📒 Files selected for processing (2)
  • .github/workflows/lighthouse-scan.yml
  • src/App.tsx

📝 Walkthrough

Walkthrough

The Lighthouse scan workflow's minimum performance threshold is lowered from 70 to 50. In App.tsx, the loading-state JSX wrapper is changed from a <div> to a <main> element, with the corresponding closing tag updated to match.

Changes

Semantic markup and CI threshold

Layer / File(s) Summary
App loading wrapper divmain
src/App.tsx
The !loaded render path wraps its children in <main> instead of <div>, and the component's final closing tag is updated to match.
Lighthouse threshold reduction
.github/workflows/lighthouse-scan.yml
min_performance input default is changed from 70 to 50.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • tehw0lf/flowdive#27: Also modifies the Lighthouse workflow's min_performance threshold input.
  • tehw0lf/flowdive#30: Also replaces the root <div> with <main> in App.tsx including the !loaded path.

Poem

🐇 A <div> once held the loading screen tight,
Now <main> steps in, semantically right.
Lighthouse asks for fifty, not seventy more,
A bunny hops past every shifting score.
Small changes, clean hops — that's what coding's for! 🌟

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main CI change by stating the Lighthouse performance threshold was lowered to 50.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/lighthouse-performance-threshold

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

@tehw0lf tehw0lf merged commit 1e0c9ed into main Jun 30, 2026
20 checks passed
@tehw0lf tehw0lf deleted the chore/lighthouse-performance-threshold branch June 30, 2026 17:13
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