Adds Lighthouse CI GitHub Action #110
Merged
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
ChrisMKindred
requested review from
jamiepaul,
Vinsanity,
dpellenwood,
JMRhodes and
lindseyolson
dpellenwood
approved these changes
Oct 16, 2023
|
@dpellenwood Yes, I will add both a readme/instructions and changelog but I need to get it merged into main first to make sure that everything runs. |
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.
Due to a limitation in GitHub actions, this will need to be merged to the main branch before running the workflow as a full test.
What does this do/fix?
This PR creates a Lighthouse CI Action that can be run via a workflow_dispatch. When the workflow runs, it will query one to many (line separated) of the URLs listed in the
urlsparam. The results will trigger an error or warning in the action UI based on the config settings in thelighthouserc.jsonfile. These settings should be customized for each production site based on the current performance. The full report is also added to the action artifacts, which can be disabled by changing theuploadArtifactsparam to false.This action aims to eventually run after deployments to test the site and trigger notifications if there are any performance, accessibility, SEO, or best practice degradations.