Issue tracker: GitLab

Issues and PRDs for this repo live as GitLab issues on the company's self-hosted GitLab instance (the host shown by git remote -v in this clone). Use the glab CLI for all operations.

Self-hosted host

This is not gitlab.com. glab must be pointed at the company host (read it from git remote -v). Either:

• Authenticate once: glab auth login --hostname <gitlab-host>, or
• Set GITLAB_HOST=<gitlab-host> in the environment for one-off commands.

Once authenticated, glab infers the project from git remote -v when run inside this clone.

Conventions

• 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 <number> --comments. Use -F json for machine-readable output.
• List issues: glab issue list -F json with appropriate --label filters.
• Comment on an issue: glab issue note <number> --message "...". GitLab calls comments "notes".
• Apply / remove labels: glab issue update <number> --label "..." / --unlabel "...". Multiple labels can be comma-separated or by repeating the flag.
• Close: glab issue close <number>. glab issue close does not accept a closing comment, so post the explanation first with glab issue note <number> --message "...", then close.
• Merge requests: GitLab calls PRs "merge requests". Use glab mr create, glab mr view, glab mr note, etc. — the same shape as gh pr ... with mr in place of pr and note/--message in place of comment/--body.

When a skill says "publish to the issue tracker"

Create a GitLab issue.

When a skill says "fetch the relevant ticket"

Run glab issue view <number> --comments.