glab-gitlab-issuelisted

# Glab Gitlab Issue Manage GitLab issues from the terminal using `glab`. ## Required Inputs Collect these inputs before running commands: - `repo`: `OWNER/REPO` or `GROUP/NAMESPACE/REPO` (example: `example-org/example-app`) - Pass plain repo path (do not pre-encode `%2F`). - The helper script auto-encodes repo path only when calling `glab api` endpoints. - `issue_id`: issue IID in that repository (example: `165`) - `author` (for commit query): GitLab username (example: `octocat`) ## Workflow 1. Confirm authentication with `glab auth status` if access is uncertain. 2. Identify intent: view, comment, assignee update, label update, or time tracking. 3. For reading an issue, use `view`; it caches GitLab `/uploads/...` files from the description and notes by default under `${XDG_CACHE_HOME:-$HOME/.cache}/codex/glab-gitlab-issue/` and rewrites them to local links in the output. 4. Return key result, including any changed fields. ## Preferred Execution Prefer the bundled helper script for consistency: ```bash bash scripts/issue.sh <action> --repo <repo> --issue <issue_id> [...flags] ``` Supported actions: - `commits`: query commit history by repo + author, return committed date/author/message - `view`: view issue; optional comments/system logs/json output; caches upload files by default - `images`: lower-level helper to refresh/list cached `/uploads/...` files from the issue description and notes - `note`: post a comment from inline text - `note-file`: post a comment