From 681d6461c1abd11d8f112e2cbeeed0d5a64f5254 Mon Sep 17 00:00:00 2001 From: Garry Tan Date: Thu, 26 Mar 2026 00:19:58 -0600 Subject: [PATCH] chore: add P2 TODO for land-and-deploy GitLab support MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Track the remaining work to support GitLab in /land-and-deploy — MR merge, CI polling, and deploy workflow detection using glab equivalents. Co-Authored-By: Claude Opus 4.6 (1M context) --- TODOS.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/TODOS.md b/TODOS.md index 1c4b88ed..3ee995b6 100644 --- a/TODOS.md +++ b/TODOS.md @@ -168,6 +168,18 @@ Linux cookie import shipped in v0.11.11.0 (Wave 3). Supports Chrome, Chromium, B ## Ship +### GitLab support for /land-and-deploy + +**What:** Add GitLab MR merge + CI polling support to `/land-and-deploy` skill. Currently uses `gh pr view`, `gh pr checks`, `gh pr merge`, and `gh run list/view` in 15+ places — each needs a GitLab conditional path using `glab ci status`, `glab mr merge`, etc. + +**Why:** Without this, GitLab users can `/ship` (create MR) but can't `/land-and-deploy` (merge + verify). Completes the GitLab story end-to-end. + +**Context:** `/retro`, `/ship`, and `/document-release` now support GitLab via the multi-platform `BASE_BRANCH_DETECT` resolver. `/land-and-deploy` has deeper GitHub-specific semantics (merge queues, required checks via `gh pr checks`, deploy workflow polling) that have different shapes on GitLab. The `glab` CLI (v1.90.0) supports `glab mr merge`, `glab ci status`, `glab ci view` but with different output formats and no merge queue concept. + +**Effort:** L +**Priority:** P2 +**Depends on:** None (BASE_BRANCH_DETECT multi-platform resolver is already done) + ### Ship log — persistent record of /ship runs **What:** Append structured JSON entry to `.gstack/ship-log.json` at end of every /ship run (version, date, branch, PR URL, review findings, Greptile stats, todos completed, test results).