GoogleChrome/lighthouse-ci
Report GitHub check status differently when highest failing assert is a warning
開放
#375 建立於 2020年7月8日
P3enhancementgood first issue
倉庫指標
- 星標
- (5,965 顆星)
- PR 合併指標
- (PR 指標待抓取)
描述
I've currently set a assert profile like this:
module.exports = {
ci: {
...
assert: {
...
assertions: {
"categories:performance": "warn",
"categories:best-practices": "warn",
"categories:seo": "warn",
"uses-long-cache-ttl": "off",
"uses-http2": "off"
}
}
}
}
What I get on github is this:
The message is fine, but having a success conclusion makes the checks panel to auto-collapse, so users won't be attracted to it at all. Maybe we should use neutral or find another way to improve that, but without failing the check?