Bug 241635
| Summary: | [GitHub] Style checker should be able to comment on the diff | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Keith Miller <keith_miller> |
| Component: | Tools / Tests | Assignee: | Jonathan Bedard <jbedard> |
| Status: | NEW | ||
| Severity: | Normal | CC: | aakash_jain, ap, bfan2, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Local Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 239082 | ||
Keith Miller
Right now there is the merge (not sure exactly what the name is) check for style. But reviewers still need to click on the details page to see if any are relevant. It could be useful to provide a button next to the details link that will have the style checker comment on the lines it thinks have issues.
We may not want this all the time because it could become quite noisy, which happened back in the day on bugzilla. Thus, a button or some other user initiated trigger would be my recommendation.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/95695974>
Sam Sneddon [:gsnedders]
Potentially we'd could create a check run and then we could actually leave annotations (which appear similar to review comments) for style check failures.
However, that requires us to be using a GitHub App to interact with GitHub, which I don't believe we do currently?
See: https://docs.github.com/en/rest/checks/runs?apiVersion=2022-11-28#:~:text=annotations,-array%20of%20objects
If we're concerned about noisiness, we could either require a button to be clicked in the GitHub check UI, or add some sort of bot command in a comment on the PR. That said, https://ews-build.webkit.org/#/builders/38 does look like it passes on the overwhelming majority of EWS runs.