trozz/Approve PR via reaction

Gate a job on an approving reaction from listed approvers (users or org teams), keyed to the PR head commit SHA.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
approversComma or whitespace separated approvers allowed to approve. Each entry is a GitHub username or an org team as org/slug (a leading @ is optional). Team members are resolved via the API, which requires the token to have read:org scope.yes
labelOptional identifier for what is being approved. Shown in the comment and used (with the commit SHA) to key the approval comment. Set distinct labels when running more than one approval gate on the same PR so their comments do not collide.no""
messageOptional free text shown near the top of the approval comment.no""
approve-reactionReaction that counts as approval. One of: +1, -1, laugh, confused, heart, hooray, rocket, eyes.no+1
reject-reactionReaction that counts as rejection. One of: +1, -1, laugh, confused, heart, hooray, rocket, eyes. Must differ from approve-reaction.no-1
min-approvalsMinimum number of distinct approver approval reactions required.no1
timeout-minutesMinutes to wait for an approval reaction before failing.no5
poll-secondsHow often to poll the approval comment for reactions.no30
tokenGitHub token used to comment and read reactions. Resolving org team members requires a token with read:org scope (a PAT or a GitHub App installation token, e.g. from actions/create-github-app-token); the default GITHUB_TOKEN cannot read team membership.no${{ github.token }}
namedescription
approved-byComma separated logins of the approvers who approved (empty if not approved).