[code-infra] Add Renovate PR report workflow - #1793
Conversation
Deploy previewBundle sizeTotal Size Change: 0B(0.00%) - Total Gzip Change: 0B(0.00%) Show details for 69 more bundles@mui/internal-docs-infra/abstractCreateDemo parsed: 0B(0.00%) gzip: 0B(0.00%) PerformanceTotal duration: 17.99 ms -4.25 ms(-19.1%) | Renders: 5 (+0) | Paint: 69.11 ms -10.41 ms(-13.1%)
5 tests within noise — details Check out the code infra dashboard for more information about this PR. |
b03a62c to
ad2533d
Compare
|
- Replace the GraphQL viewer lookup, which fails for installation tokens, with an explicit comment-author input; the fleet workflow derives it from the App slug and the reusable workflow defaults to github-actions[bot]. - Match report comment authors exactly instead of stripping the [bot] suffix, so a same-named user account cannot forge the sticky state. - Let the report degrade to heuristics when the Claude step fails. - Share the state-comment serializer between renderer and parser, and cover the announce flow with round-trip tests.
ffcc814 to
f71e146
Compare
Summary
@mui/infrais mentioned when a PR needs attention; when a later run reports a materially different issue (breaking status, security flag, culprit dependency, or CI culprit — not reason wording), the comment is recreated so the mention pings again.Example of the sticky comment on a PR:
Test plan
pnpm test --run renovatePrReportpnpm test --runpnpm release:buildpnpm typescriptThe aggregate report below is written to the action run's job summary only (it is not posted as a comment anywhere) —