From 3bb0b1b917b25c3c413c5d9df3df7fcfbb34e7ba Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Thu, 7 May 2026 07:20:57 +0100 Subject: [PATCH] Update issue listing command in GitLab documentation for clarity --- .../setup-matt-pocock-skills/issue-tracker-gitlab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/engineering/setup-matt-pocock-skills/issue-tracker-gitlab.md b/skills/engineering/setup-matt-pocock-skills/issue-tracker-gitlab.md index 1993c58..f54da95 100644 --- a/skills/engineering/setup-matt-pocock-skills/issue-tracker-gitlab.md +++ b/skills/engineering/setup-matt-pocock-skills/issue-tracker-gitlab.md @@ -6,7 +6,7 @@ Issues and PRDs for this repo live as GitLab issues. Use the [`glab`](https://gi - **Create an issue**: `glab issue create --title "..." --description "..."`. Use a heredoc for multi-line descriptions. Pass `--description -` to open an editor. - **Read an issue**: `glab issue view --comments`. Use `-F json` for machine-readable output. -- **List issues**: `glab issue list --state opened -F json` with appropriate `--label` filters. Note that GitLab uses `opened` (not `open`) for the state value. +- **List issues**: `glab issue list -F json` with appropriate `--label` filters. - **Comment on an issue**: `glab issue note --message "..."`. GitLab calls comments "notes". - **Apply / remove labels**: `glab issue update --label "..."` / `--unlabel "..."`. Multiple labels can be comma-separated or by repeating the flag. - **Close**: `glab issue close `. `glab issue close` does not accept a closing comment, so post the explanation first with `glab issue note --message "..."`, then close.