Next (Review, Feedback)

[alekseykulikov]

Overview for the v2.3.0 release. Please give us your feedback. The tradition of huge rewrites goes on 🚀

Goals:

• A better way to communicate results: automatic annotations, slack notification on failure, simple option to collect artifacts for later reuse. #2 #17 #28 #11
• Integrate with newest features in LHCI and Github Actions: upload artifacts automatically, integrate with annotations, --uploadUrlMap to provide compare report automatically, yaml config
• Improve docs to explain the main benefits and features.

Expecte workflow: setup action with budgets and temporary storage, get notification when something breaks (example):

Changes:

• major Automatic action annotations for failed assertions
• major uploadArtifacts upload artifacts from the action, instead of extra config, using @actions/artifact
• Rename upload.* to serverBaseUrl and serverToken with backward compatibility
• Add .yaml config support
• Add support for LHCI's --uploadUrlMap, but it does not work
• Refactoring some code to utils
• Support for urls in config #29

Notes:

• This PR is only for review. Due to the massive node_modules folder, it's not possible to review the actual changes. So, I reset node_modules from the master but kept all the code changes.
• The working code is ready for testing: https://github.com/treosh/lighthouse-ci-action/tree/next.
• The README.md and recipes are work in progress.
• The Netlify integration will be closed using community actions #30 #31 (instead of the custom option)

[alekseykulikov]

A lot of time and experiments went to a simple solution for #2 : communicate failed asserts using annotations and attach results to the job.

@denar90 and I think this workflow is close to ideal :) @exterkamp @paulirish let us know what you think.

[alekseykulikov]

Thank you @exterkamp for a review 👍All the suggestions are in the next branch and going to be merged to master soon.