Run and archive lighthouse report on Circle CI artifact #208
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks! Let's see how this goes when merged in master |
|
It seems to give a timeout: https://github.com/pandas-dev/pydata-sphinx-theme/runs/798177183?check_suite_focus=true |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a smaller version of #206: as discussed over there, PRs that change the
archiveworkflow are kind of hard to evaluate, so this only adds:larsoner/circleci-artifacts-redirector-actionurlfoo-software/lighthouse-check-actionto run the report against theurlindex.html... for nowactions/uploadto archive the report to get an idea of the as-is state of the reportFuture PRs will shave off more pieces of #206:
foo-software/lighthouse-check-status-actionto validate against the top-level scores (simple 0-100 integers) to prevent regressions