f931dcd1bfThe previous status-job pattern (inline shell that exits 1 when 'approved' is missing) shows a red failed check on every fresh PR. GitHub Actions jobs only have pass/fail — there's no way to express 'pending' via exit code. The new sub-action uses the commit-status API to set state=pending until the approved label appears. Hold label produces state=failure. The status job itself now always succeeds; the commit status it creates is what branch protection enforces. Caller workflow swaps the 20-line jq+exit block for a one-line uses: call, adds statuses:write to permissions, and marks 'slash-commands/approval' as a required status check (replacing the job-based check).
1 KiB
1 KiB
actions
GitHub Actions relevant to the management of MCP repositories.
Actions
| Action | Description |
|---|---|
cloudflare-pages-preview/deploy |
Deploy a static HTML directory to Cloudflare Pages under a per-PR branch alias, inject noindex headers, and post a sticky PR comment with preview URLs |
cloudflare-pages-preview/cleanup |
Delete Cloudflare Pages deployments for a closed PR's branch alias and update the sticky comment |
hugo-build |
Install Go + Hugo extended and build a Hugo site (preview or production mode) |
slash-commands |
Handle /lgtm, /hold, and /stageblog PR slash commands gated by team membership + CODEOWNERS; invalidate approval on push |
slash-commands/status |
Set a pending/success/failure commit status based on approval/hold labels — yellow pending check until /lgtm, not red |