Patrick Hulce

Thanks for filing @bobbygryzynger! That's largely because we haven't really committed to a stable REST API intended for public consumption. The [only real contract right now](https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/migration-guide.md#server-cli-version-compatibility) is that the CLI...

Thanks for filing @jean13360! > We can see two browser : one for lighthouse test and one for puppeteer .. how to reuse the pupeeteer browser excuted by lighthouse-ci ?...

Thanks for filing @idbartosz ! > Is there a reason why runGithubStatusCheck wasn't added for runFilesystemTarget? We don't run the status check because there's nothing for the status check to...

> And those are accessible via URL which could be set as a status details link I don't think there's any way for LHCI to figure this out in a...

Thanks for filing @ptmkenny! Does this work for you? ``` assert: assertMatrix: - matchingUrlPattern: "devserver.com" preset: "lighthouse:recommended" assertions: is-crawlable: - off # Dev servers are not crawlable.

Ah, I see. The entries in assertMatrix don't override each other. They're additive. `assertMatrix` + `matchingUrlPattern` is like saying "for all URLs that match this pattern, always assert at least...

Got it 👍 > I was trying to find a way to define a set of default, very strict criteria and then make a list of exceptions from certain tests...

Thanks for filing @MikeSperone! You are correct there is no dashboard UI or necessary backend machinery to display a summary of plugin categories in the dashboard. It's not a bug...

Definitely related to https://github.com/GoogleChrome/lighthouse-ci/issues/158 though I think this is actually slightly simpler. We're not custom creating new metric graphs or anything, just similar category breakdowns to what we're already seeing...

> If you think this is a good idea, I'll try to make a PR. Or if you have a better way in mind, please let me know, cause we...