PR Status Comment
Post or update a single sticky PR comment summarizing your CI job statuses as a table — one bot
comment per PR that updates in place across pushes, instead of a new comment piling up every run.
This action builds the table (and any extra Markdown sections you pass in) from your job results;
posting itself is delegated to
marocchino/sticky-pull-request-comment.
Requirements
Section titled “Requirements”- The calling job needs
permissions: pull-requests: write(notissues: write— the underlying action’s permission manifest requirespull-requests: writespecifically, and without it the comment step fails withResource not accessible by integration, even though the REST endpoint it hits is nominallyissues/comments).
Inputs
Section titled “Inputs”- jobs (required): JSON object mapping a display label to a status, e.g.
{"🧾 Conventional Commits": "success", "🏗️ Build": "failure"}. Useneeds.<job>.resultfor each entry — GitHub Actions exposes this natively, no customoutputs.statusplumbing needed in the upstream jobs. - extra-markdown: Additional Markdown appended after the status table (default: none). Use this for repo-specific sections (coverage, mutation testing, benchmarks, …) instead of reimplementing the table logic per repo.
- comment-header: Header used to identify the sticky comment to update (default:
PR Validation). Only relevant if you post more than one sticky comment on the same PR. - github-token: Token used to create/update the comment (default:
github.token).