We scan this tool’s changelog a few times a day and keep the changes that would alter your agent’s next action: 34 since March 2026, each linked to its source.
glabWhen cloning a group’s repositories while excluding subgroup projects, run `glab repo clone` with `--group`, `--exclude-subgroup`, and `--paginate`.
glab repo clone -g <group> --exclude-subgroup <subgroup-path> --paginateWhen updating an issue’s time tracking, use `glab issue update` with the estimate or time-spent flags; durations use GitLab time-tracking format. Use the removal flags to reset either value.
glab issue update <issue-id> --estimate 2d --spend 1h30mWhen reviewing a merge request, create a project-member-only note with `glab mr note create <mr-id> --message "<message>" --internal`. To add it to an existing discussion, include `--reply <discussion-id>`.
glab mr note create <mr-id> --message "<message>" --internalWhen running Cargo package operations, invoke Cargo through glab’s Dependency Firewall to check package transfers against the current project’s policy. Use `glab dependency-firewall cargo` and pass the Cargo arguments to it.
glab dependency-firewall cargo fetchWhen creating or updating a GitLab work item, issue, or merge request with a local file to include, pass the file path with `--attach` to upload it and add its reference to the description.
glab work-items create --type issue --title "<title>" --attach <local-file>When authenticating a project to GitLab Artifact Registry, run `glab artifact-registry login` with the registry URL and the option for its package manager: `--gradle`, `--npm`, `--sbt`, or `--maven`. [GitLab CLI docs](https://docs.gitlab.com/cli/artifact-registry/login/)
glab artifact-registry login --gradle --registry <repository_url>When creating or updating an issue, merge request, or work item with a description from a file, pass `--description-file <file>` to that command; use `-` to read from standard input.
glab issue create -t "<title>" --description-file <file>When authenticating Docker to a GitLab Artifact Registry, register glab as its credential helper with `glab artifact-registry login --docker --registry <registry_host>`. The helper exchanges a fresh token for each pull or push and ignores `GITLAB_TOKEN`.
glab artifact-registry login --docker --registry <registry_host>When importing project or group CI/CD variables, provide a JSON array in the shape emitted by `glab variable export --output json`; use `--input-file` for a file or pipe JSON on standard input. By default, import targets the current project and errors if a variable already exists; use `--skip-existing` to continue past existing variables.
glab variable import --input-file variables.jsonWhen a project already has the secure file, run `glab securefile update <name> <path> [flags]` to replace its contents. If the contents are unchanged, no update occurs; the update changes the file ID, so later downloads should use `--name`.
glab securefile update "<name>" "<local-path>"