ci: re-enable Lighthouse workflow when multei.com.br is back online
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Context
The Lighthouse GitHub Actions workflow audits https://multei.com.br on every push. Production currently fails LHCI collect with CHROME_INTERSTITIAL_ERROR (Chrome interstitial / site unavailable), so the workflow was temporarily disabled (trigger changed from push to workflow_dispatch only).
Related:
- Toolchain fix: #418
- Example failing collect after Action upgrades: https://github.com/multei/web/actions/runs/29500972827
Goal
Re-enable automatic Lighthouse runs on push once https://multei.com.br loads cleanly without a Chrome interstitial.
Suggested scope
- Confirm https://multei.com.br responds successfully in a clean browser (no SSL/DNS/interstitial warning).
- In
.github/workflows/lighthouse.yml, restoreon: [push](keepworkflow_dispatchoptional if useful). - Remove or update the temporary-disable comments in that file.
- Trigger a workflow run and confirm LHCI collect + artifact upload succeed.
- Clear or update the related notes in
TROUBLESHOOTING.mdif the interstitial issue is resolved.
Acceptance criteria
- Lighthouse workflow runs automatically on push again.
- A recent run is green (or fails only on real Lighthouse score/assertions, not interstitial/toolchain).
-
lighthouseresultsartifact is published.
Notes
- Do not re-enable on
pushwhile the production URL still shows an interstitial or is otherwise unreachable to Chrome.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
First check https://multei.com.br in a clean browser and review the failing collect run linked in the issue. Then inspect .github/workflows/lighthouse.yml and the related notes in TROUBLESHOOTING.md. Done means push-triggered Lighthouse runs are restored, a recent run completes without an interstitial failure, and the lighthouseresults artifact is published.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100