96c6283aa5/lgtm now only accepts members of always-allow-teams (core-maintainers by default) — CODEOWNERS no longer grants /lgtm authorization. /hold and /stageblog keep the team-or-CODEOWNERS rule. On a successful /lgtm the action now: - adds the accepted label (renamed from approved) - submits the bot APPROVE review - enables auto-merge (new) Auto-merge is disabled on /lgtm cancel and on push invalidation. If the PR is already mergeable when auto-merge is enabled, the action merges directly instead. This shifts the merge gate from the slash-commands/approval commit status to GitHub's native required-reviews + auto-merge. The commit status is now optional (set status-context to empty to skip). The status sub-action is documented as optional for callers who want to keep status-check-based gating. New inputs: enable-auto-merge (default true), auto-merge-method (default squash).
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 (core-maintainers only: label + approve + auto-merge), /hold, and /stageblog PR slash commands; invalidate approval on push |
slash-commands/status |
Optional: set a pending/failure commit status for callers using status-check-based gating instead of required-reviews + auto-merge |