badsyntax/Issue Comment (Handlebars)
Comment on a GitHub issue using a Handlebars template
View on GitHubTrust Signals
- Scorecard Score
- Scorecard 2–4scored Jul 6, 2026
- Maintenance Recency
- Stalelast commit Jan 17, 2023
- License
- MIT
Pinned Snippet
uses: badsyntax/github-action-issue-comment@1ffcdf2db6a2afa72a51b9ec5f77b1f0cac43fab # v1.0.2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| action | Action, one of "update", "create", "delete", or "create-clean". The "create-clean" action will first delete the existing comment, then create a new comment | yes | — |
| template | The path to the handlebars template file, if not using the body options (optional). For example: ./.github/pr-comment-template.hbs | no | "" |
| body | The comment body, if not using the template option (optional). For example: "a message" | no | "" |
| template-inputs | A JSON object of key value pairs (required only if using the template option). For example: {"key":"value"} | no | "" |
| id | The unique id to track the comment. For example: deploy | yes | — |
| issue-number | The GitHub issue number. For example: 1 | yes | — |
| token | GITHUB_TOKEN (issues: write, pull-requests: write) or a repo scoped PAT | yes | — |
Outputs
no outputs