-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
CSV and excel reporters for CI #63
Comments
I'd prefer a CSV, but whatever. Both can be good. I like the output from https://github.com/cloudfour/lighthouse-parade |
Thanks for the references, it's a good idea. Will work on this when I have some free time. PRs very much welcome in the mean time. FYI running the |
Great to hear that the data/scores may be exported easily, especially for those of us that may want a historical perspective when publishing new releases to see if any areas have regression in score. |
Just pointing out that I have nothing against CSV and mentioned JSON just as an example format in the OP. |
CSV is just easier to import into a spreadsheet, which is how many of these reports are going to need to be processed. Great about unlighthouse-ci - when I try to run it though I get:
|
Never mind. It's working when I RTFM https://unlighthouse.dev/integrations/ci |
I think there are two issues here:
For now I've updated this issue to just cover issue 1. Feel free to make a separate issue for the GitHub action if it's more appropriate |
CSV is now supported in v0.9.0, have moved GitHub Action Support to this issue. Please let me know you're feedback, will look to improve it. |
Clear and concise description of the problem
I would like to use the results of the the Lighthouse scan in CI to automatically comment on PRs with the scores. The static HTML is great, but just having the main scores as output of the CLI program will be awesome.
This action has some examples - https://github.com/foo-software/lighthouse-check-action
Suggested solution
I would imagine a flag
--output-scores
that saves ascores.json
file. For the actual implementation, I am not sure how to achieve it.Alternative
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: