merge-green

name	merge-green
metadata	{"version":"0.24.6"}
description	Merge PRs only when all quality gates pass. Use whenever asked to merge a PR, complete a merge, or land a branch — polls checks every 5 minutes until green instead of merging blind or bypassing.

Merge when green

The default, always: a PR merges only when every check is green. Pending means wait; failing means fix. There is no third option.

1. GitHub: run plugin/scripts/merge-when-green.sh <pr> [interval] [max] (defaults: 300 s × 24) — in the background, so work continues while it polls. In this repo the script lives at plugin/scripts/; in plugin-installed sessions use "${CLAUDE_PLUGIN_ROOT}/scripts/merge-when-green.sh".
2. Other platforms: same rule via their CLI; prefer native merge-when-green (glab mr merge --when-pipeline-succeeds, ADO auto-complete).
3. After a merge: pull the base branch, delete the merged local branch, sync tickets if items closed, regenerate the roadmap if the log changed.
4. On red gates: report which checks failed and fix them. Never merge with --admin, never skip a gate, never retry-until-flaky-passes without understanding the failure.
5. Auto-merge flag: features.auto_merge_on_green in .work/config.yml (default true). False = advisory mode: the script polls, reports green, does NOT merge — a human runs gh pr merge <pr> --merge. Overrides, strongest first: --auto/--advisory as the script's first argument (one run), then WORKLOG_AUTO_MERGE=1|0, then the config. Red/pending/timeout behavior is unchanged either way.