-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Add Lighthouse check in CI #971
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
Labels
Comments
Sounds great! |
BrunnerLivio
added a commit
to BrunnerLivio/docs.nestjs.com
that referenced
this issue
Apr 19, 2020
BrunnerLivio
added a commit
to BrunnerLivio/docs.nestjs.com
that referenced
this issue
May 1, 2020
BrunnerLivio
added a commit
to BrunnerLivio/docs.nestjs.com
that referenced
this issue
May 1, 2020
BrunnerLivio
added a commit
to BrunnerLivio/docs.nestjs.com
that referenced
this issue
May 2, 2020
BrunnerLivio
added a commit
to BrunnerLivio/docs.nestjs.com
that referenced
this issue
May 23, 2020
BrunnerLivio
added a commit
to BrunnerLivio/docs.nestjs.com
that referenced
this issue
May 23, 2020
BrunnerLivio
added a commit
to BrunnerLivio/docs.nestjs.com
that referenced
this issue
May 23, 2020
BrunnerLivio
added a commit
to BrunnerLivio/docs.nestjs.com
that referenced
this issue
May 23, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm submitting a...
Current behavior
Currently we do not track how well the documentation scores on Lighthouse
Expected behavior
Let’s track it using the lighthouse-ci
What is the motivation / use case for changing the behavior?
To improve A11Y and performance
Other
Let’s use Lighthouse Github Actions to add this in a breeze. Should work per PR thanks to Netlify deploy preview.
The text was updated successfully, but these errors were encountered: