-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run Lighthouse checks during CI #6
Comments
I'm interested in working on this issue! Plan to work on this the week of 5/6 |
@deweydell - Lighthouse set up requires us to add a bot as a contributor to our repo! I don't believe I have the permissions to do so on this repository. |
Update 5/18: Continue to remain blocked, but now with a new blocker! Please see PR #47 for details. |
@halfghaninne I recently decided to check out github actions -- could be a potential solution there for this issue. Haven't dove into it, but maybe something like this: https://github.com/marketplace/actions/lighthouse-ci-action if you ever decide to pick this up in the future. |
Description
We want to monitor that changes to the website do not negatively affect our SEO, performance, accessibility, or progressive web app features.
Because Lighthouse GH integration only works with Travis CI, this issue is dependent on #14.
Acceptance Criteria
Resources
https://github.com/GoogleChromeLabs/lighthousebot
The text was updated successfully, but these errors were encountered: