### Guided Onboarding for Orbit

Source: https://docs.gitlab.com/cli/orbit

Initiates a guided setup process to verify access, install the Orbit skill, and set up the local CLI.

```bash
glab orbit setup
```

--------------------------------

### Compact output for agents

Source: https://docs.gitlab.com/cli/orbit/remote/graph-status

This example demonstrates how to get a compact output format suitable for agents by using the `--format llm` flag.

```bash
# Compact output for agents
$ glab orbit remote graph-status --full-path gitlab-org/gitlab --format llm
```

--------------------------------

### Example: Publish Catalog with Tag

Source: https://docs.gitlab.com/cli/repo/publish/catalog

This example demonstrates how to publish CI/CD components using a specific tag name.

```bash
glab repo publish catalog v1.2.3
```

--------------------------------

### Start glab mcp serve

Source: https://docs.gitlab.com/cli/mcp/serve

Execute this command in your console to start the Model Context Protocol server with stdio transport.

```console
glab mcp serve

```

--------------------------------

### Install GitLab Duo CLI Binary

Source: https://docs.gitlab.com/cli/duo/cli

Install the Duo CLI binary using the `--install` flag. The `--yes` flag can be used to skip confirmation prompts.

```bash
# Install the Duo CLI binary
glab duo cli --install
```

```bash
# Install the Duo CLI binary without prompts
glab duo cli --install --yes
```

--------------------------------

### Install Core Skill Globally

Source: https://docs.gitlab.com/cli/skills/install

Installs the core `glab` skill for the current user in the global `~/.agents/skills/` directory.

```bash
glab skills install --global
```

--------------------------------

### Install Orbit local CLI binary without prompts

Source: https://docs.gitlab.com/cli/orbit/local

Installs the Orbit local CLI binary without running it and skips all confirmation prompts. Ideal for automated setups.

```bash
glab orbit local --install --yes
```

--------------------------------

### Inspect Indexing Progress Example

Source: https://docs.gitlab.com/cli/orbit/remote

An example command to check the indexing progress for a specific project within the GitLab Knowledge Graph.

```console
# Inspect indexing progress
$ glab orbit remote graph-status --full-path gitlab-org/gitlab
```

--------------------------------

### Example: Load Zsh Completions and Define Completion Function

Source: https://docs.gitlab.com/cli/completion

This example demonstrates loading completions in the current zsh session and defining the `_glab` completion function.

```shell
# Load completions in the current zsh session
source <(glab completion -s zsh); compdef _glab glab
```

--------------------------------

### Example of Switching Stacks

Source: https://docs.gitlab.com/cli/stack/switch

This example demonstrates how to use the `glab stack switch` command to switch to a specific stack. Replace `<stack-name>` with the actual name of your stack.

```bash
glab stack switch <stack-name>
```

--------------------------------

### Get Glamour Style Configuration

Source: https://docs.gitlab.com/cli/config/get

Retrieves the value of the 'glamour_style' configuration key. This example demonstrates fetching the configured style for output formatting.

```bash
$ glab config get glamour_style
notty
```

--------------------------------

### Examples of glab repo search

Source: https://docs.gitlab.com/cli/repo/search

Demonstrates how to use the `glab repo search` command with different aliases and the search flag.

```bash
glab project search -s "title"
glab repo search -s "title"
glab project find -s "title"
glab project lookup -s "title"
```

--------------------------------

### Example Usage of `glab orbit remote dsl`

Source: https://docs.gitlab.com/cli/orbit/remote/dsl

This example demonstrates how to execute the `glab orbit remote dsl` command to fetch the schema.

```bash
$ glab orbit remote dsl

```

--------------------------------

### Discovery Workflow Examples

Source: https://docs.gitlab.com/cli/orbit/remote

A sequence of commands to initiate the discovery process for the GitLab Knowledge Graph, starting with checking service status and schema.

```console
# Discovery workflow (always start here)
$ glab orbit remote status
$ glab orbit remote schema
$ glab orbit remote schema User Project MergeRequest
$ glab orbit remote dsl
$ glab orbit remote tools
```

--------------------------------

### Install Orbit local CLI binary

Source: https://docs.gitlab.com/cli/orbit/local

Installs the Orbit local CLI binary without immediately running it. Use this to prepare the environment.

```bash
glab orbit local --install
```

--------------------------------

### Execute glab stack prev

Source: https://docs.gitlab.com/cli/stack/prev

This example shows how to execute the `glab stack prev` command. This command is experimental and may be unstable.

```bash
glab stack prev

```

--------------------------------

### Run Non-Interactive Orbit Setup

Source: https://docs.gitlab.com/cli/orbit/setup

Use the `--yes` flag to automatically accept all prompts during the setup process, making it non-interactive.

```bash
glab orbit setup --yes
```

--------------------------------

### Install Core Glab Skill

Source: https://docs.gitlab.com/cli/skills/install

Installs the default core `glab` skill to the current project's `.agents/skills/` directory. This is the default behavior when no skill name is provided.

```bash
glab skills install
```

--------------------------------

### List GitLab Issues

Source: https://docs.gitlab.com/cli/issue

Use this command to list all issues in the current repository. No specific setup is required beyond having the GitLab CLI installed and authenticated.

```console
glab issue list
```

--------------------------------

### Get Editor Configuration

Source: https://docs.gitlab.com/cli/config/get

Retrieves the value of the 'editor' configuration key. This example shows how to get the configured text editor.

```bash
$ glab config get editor
vim
```

--------------------------------

### Install Skill to Custom Directory

Source: https://docs.gitlab.com/cli/skills/install

Installs a specified skill, like `glab-stack`, to a custom directory path. The path is resolved relative to the current working directory.

```bash
glab skills install glab-stack --path /path/to/skills
```

--------------------------------

### Install Orbit Skill Globally

Source: https://docs.gitlab.com/cli/orbit/setup

Install the Orbit skill at the user scope (~/.agents/skills/) instead of in the current repository using the `--global` flag.

```bash
glab orbit setup --global
```

--------------------------------

### Look up indexing progress by full path

Source: https://docs.gitlab.com/cli/orbit/remote/graph-status

Use this example to check the indexing status of a project or group by providing its full path.

```bash
# Look up indexing progress by full path
$ glab orbit remote graph-status --full-path gitlab-org/gitlab
```

--------------------------------

### glab ci get Command Synopsis

Source: https://docs.gitlab.com/cli/ci/get

The basic syntax for the `glab ci get` command, showing available flags.

```console
glab ci get [flags]
```

--------------------------------

### Update all installed skills

Source: https://docs.gitlab.com/cli/skills/update

Use the --all flag to update every skill that is currently installed in the well-known locations.

```bash
glab skills update --all
```

--------------------------------

### Install Specific Bundled Skill

Source: https://docs.gitlab.com/cli/skills/install

Installs a specific bundled skill by its name, such as `glab-stack`, to the current project's `.agents/skills/` directory.

```bash
glab skills install glab-stack
```

--------------------------------

### Create a Scheduled Pipeline with Variables

Source: https://docs.gitlab.com/cli/schedule/create

This example demonstrates how to create a pipeline schedule and pass custom variables to it. Use the `--variable` flag multiple times for additional key-value pairs.

```bash
glab schedule create --cron "0 0 * * *" --description "Daily build" --ref main --variable "foo:bar" --variable "baz:qux"
```

--------------------------------

### Run a Query from a File

Source: https://docs.gitlab.com/cli/orbit/remote

Example of executing a GitLab Knowledge Graph query by specifying the path to a local JSON query file.

```console
# Run a query from a file
$ glab orbit remote query ./query.json
```

--------------------------------

### Install Fish Completions for Every New Session

Source: https://docs.gitlab.com/cli/completion

To permanently load Fish completions for every new session, redirect the output of `glab completion -s fish` to `~/.config/fish/completions/glab.fish`.

```shell
glab completion -s fish > ~/.config/fish/completions/glab.fish
```

--------------------------------

### Get Secure File Details Using Alias

Source: https://docs.gitlab.com/cli/securefile/get

Demonstrates using the 'show' alias to retrieve secure file details by ID.

```console
glab securefile show 1
```

--------------------------------

### Run the Orbit local CLI

Source: https://docs.gitlab.com/cli/orbit/local

Executes the Orbit local CLI. This is the basic command to start the local CLI.

```bash
glab orbit local
```

--------------------------------

### CI/CD Manual Login Setup

Source: https://docs.gitlab.com/cli/auth/login

Provides a manual login configuration for CI/CD environments when auto-login is not suitable or a personal access token is required. It uses the CI server's FQDN and job token.

```bash
glab auth login --hostname $CI_SERVER_FQDN --job-token $CI_JOB_TOKEN --api-protocol $CI_SERVER_PROTOCOL
```

--------------------------------

### Look up indexing progress by project ID

Source: https://docs.gitlab.com/cli/orbit/remote/graph-status

Use this example to check the indexing status of a project by providing its numeric ID.

```bash
# Or by numeric ID
$ glab orbit remote graph-status --project-id 278964
```

--------------------------------

### List Secure Files in Current Project

Source: https://docs.gitlab.com/cli/securefile/list

Use this command to view all secure files configured for the current project. No additional setup is required.

```bash
glab securefile list
```

--------------------------------

### Show GitLab CLI Version

Source: https://docs.gitlab.com/cli

Display the installed version of the glab CLI tool.

```bash
-v, --version
```

--------------------------------

### Show glab Version Information

Source: https://docs.gitlab.com/cli/version

Use this command to display the installed glab version and the commit it was built from. Include this information when reporting a bug.

```bash
glab version
```

--------------------------------

### Start Interactive Login

Source: https://docs.gitlab.com/cli/auth/login

Initiates an interactive login process. If within a Git repository, glab can detect and suggest GitLab instances from remotes.

```bash
glab auth login
```

--------------------------------

### CI/CD Auto-Login Setup

Source: https://docs.gitlab.com/cli/auth/login

Enables CI auto-login for most cases, allowing commands like `release list` to use CI job tokens automatically. This is the preferred method for CI/CD environments.

```bash
GLAB_ENABLE_CI_AUTOLOGIN=true glab release list -R $CI_PROJECT_PATH
```

--------------------------------

### Install Bash Completions for Linux

Source: https://docs.gitlab.com/cli/completion

To permanently load Bash completions for every new session on Linux, redirect the output of `glab completion -s bash` to `/etc/bash_completion.d/glab`.

```shell
glab completion -s bash > /etc/bash_completion.d/glab
```

--------------------------------

### Retrieve Stored Credentials for a Registry

Source: https://docs.gitlab.com/cli/auth/docker-helper

Docker automatically invokes the helper for 'store', 'get', and 'erase' actions. This example shows how to retrieve stored credentials for a specific registry.

```console
echo registry.gitlab.com | glab auth docker-helper get
```

--------------------------------

### Create a release using notes from a file

Source: https://docs.gitlab.com/cli/release/create

Specify a file to read release notes from, allowing for longer or pre-formatted notes.

```console
glab release create v1.0.1 -F changelog.md
```

--------------------------------

### glab ci get Aliases

Source: https://docs.gitlab.com/cli/ci/get

Lists the available aliases for the `glab ci get` command.

```console
stats
```

--------------------------------

### View Release with Options

Source: https://docs.gitlab.com/cli/release/view

Demonstrates viewing release information with options for filtering JSON output or opening in a web browser.

```console
# View the latest release of a GitLab repository
glab release view

# View a release with specified tag name
glab release view v1.0.1

```

--------------------------------

### Create New Stack with Specific Name

Source: https://docs.gitlab.com/cli/stack/infer

This example shows how to create a new stack with a custom name by inferring layers from a specified commit range.

```bash
glab stack infer --name feature-stack main..HEAD
```

--------------------------------

### List Deploy Keys with IDs

Source: https://docs.gitlab.com/cli/deploy-key/list

To include the unique identifier for each deploy key in the output, use the `--show-id` flag. This ID is useful for subsequent operations like getting or deleting specific keys.

```bash
glab deploy-key list --show-id
```

--------------------------------

### Create a runner controller with default settings

Source: https://docs.gitlab.com/cli/runner-controller/create

Use this command to create a runner controller with all default configurations. This is the simplest way to initiate the creation process.

```console
glab runner-controller create
```

--------------------------------

### List All Repositories on the Instance

Source: https://docs.gitlab.com/cli/repo/list

Use the `--all` flag to list all projects on the GitLab instance, removing the ownership filter. Results are paginated.

```bash
glab repo list --all
```

--------------------------------

### Show Help for `glab stack create`

Source: https://docs.gitlab.com/cli/stack/create

Inherited flag to display help information for the `glab stack create` command.

```bash
glab stack create --help
```

--------------------------------

### Show Help for repo list command

Source: https://docs.gitlab.com/cli/repo/list

Display detailed help information for the `glab repo list` command, including all available flags and options.

```bash
glab repo list --help
```

--------------------------------

### Check for and install Orbit CLI updates

Source: https://docs.gitlab.com/cli/orbit/local

Checks for and installs any available updates for the Orbit local CLI binary. Ensures you are using the latest version.

```bash
glab orbit local --update
```

--------------------------------

### Show GitLab CLI Help

Source: https://docs.gitlab.com/cli

Display help information for the glab command.

```bash
-h, --help
```

--------------------------------

### Get GPG Key in JSON Output

Source: https://docs.gitlab.com/cli/gpg-key/get

To get the full GPG key object, use the `--output json` flag. This is useful for programmatic access or when more detailed information is required.

```bash
glab gpg-key get 7750633 --output json
```

--------------------------------

### Show specific resources (compact)

Source: https://docs.gitlab.com/cli/cluster/graph

A more compact way to specify multiple resources like pods and configmaps using comma-separated values within curly braces.

```console
glab cluster graph -R user/project -a 123 -r={pods,configmaps}
```

--------------------------------

### Example Usage of glab orbit remote status

Source: https://docs.gitlab.com/cli/orbit/remote/status

This example demonstrates how to run the `glab orbit remote status` command to view the cluster health. It prints the response as pretty-printed JSON.

```bash
$ glab orbit remote status

```

--------------------------------

### Select Repository Option

Source: https://docs.gitlab.com/cli/cluster

Use this option to specify a different repository for the command. You can use the owner/repo format or the full URL.

```bash
  -R, --repo string   Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted.
```

--------------------------------

### Get a group variable

Source: https://docs.gitlab.com/cli/variable/get

Retrieves the value of a variable from a specified group.

```bash
glab variable get -g GROUP VAR_KEY
```

--------------------------------

### Show Help for docker-helper Command

Source: https://docs.gitlab.com/cli/auth/docker-helper

Displays help information for the `glab auth docker-helper` command, including available flags.

```console
glab auth docker-helper --help
```

--------------------------------

### Get a project variable

Source: https://docs.gitlab.com/cli/variable/get

Prints the value of a single variable by key for the current project.

```bash
glab variable get VAR_KEY
```

--------------------------------

### Get a group milestone

Source: https://docs.gitlab.com/cli/milestone/get

Retrieves a milestone by its ID from a specified group, identified by its name.

```console
glab milestone get 123 --group example-group
```

--------------------------------

### Select another repository

Source: https://docs.gitlab.com/cli/opentofu/state/lock

Use the `-R` or `--repo` flag to specify a different repository for the command. You can use `OWNER/REPO`, `GROUP/NAMESPACE/REPO`, or a full URL.

```bash
glab opentofu state lock --repo OWNER/REPO production
```

--------------------------------

### Show Help for glab ci config

Source: https://docs.gitlab.com/cli/ci/config

Displays help information for the `glab ci config` command, including inherited options.

```bash
  -h, --help          Show help for this command.
  -R, --repo string   Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted.
```

--------------------------------

### Delete Pipelines by Status

Source: https://docs.gitlab.com/cli/ci/delete

Remove all CI/CD pipelines that have a specific status, for example, 'failed'.

```bash
glab ci delete --status=failed
```

--------------------------------

### Get a milestone from the current project

Source: https://docs.gitlab.com/cli/milestone/get

Retrieves a milestone using its ID from the current project context.

```console
glab milestone get 123
```

--------------------------------

### Show Help for OpenTofu State Command

Source: https://docs.gitlab.com/cli/opentofu/state

Displays help information for the `glab opentofu state` command and its subcommands. Use this to understand available options and subcommands.

```bash
glab opentofu state --help
```

--------------------------------

### List current project's access tokens in JSON format

Source: https://docs.gitlab.com/cli/token/list

Use this command to list access tokens for the current project, with the output formatted as JSON.

```console
glab token list --output json
```

--------------------------------

### Subscribe to an incident using an alias

Source: https://docs.gitlab.com/cli/incident/subscribe

This example demonstrates using the 'sub' alias for the subscribe command.

```console
glab incident sub 123
```

--------------------------------

### Get a milestone as JSON

Source: https://docs.gitlab.com/cli/milestone/get

Retrieves a milestone by its ID and formats the output as JSON, suitable for programmatic use.

```console
glab milestone get 123 --output json
```

--------------------------------

### Get a milestone from a different project

Source: https://docs.gitlab.com/cli/milestone/get

Retrieves a milestone by its ID from a specified project, identified by its owner and repository name.

```console
glab milestone get 123 --project owner/project
```

--------------------------------

### Get Label Info by ID

Source: https://docs.gitlab.com/cli/label/get

Retrieves information for a specific label using its numeric ID in the current repository.

```bash
glab label get 1234
```

--------------------------------

### Show help for glab todo command

Source: https://docs.gitlab.com/cli/todo

Displays help information for the 'glab todo' command, including inherited options.

```bash
glab todo --help
```

--------------------------------

### List Instance Variables

Source: https://docs.gitlab.com/cli/variable/list

Lists environment variables for the entire GitLab instance. Use the `--instance` or `-i` flag.

```bash
glab variable list -i
```

--------------------------------

### Update a specific skill

Source: https://docs.gitlab.com/cli/skills/update

Use this command to update a specific skill, like the bundled 'glab' skill, in all locations where it is installed.

```bash
glab skills update glab
```

--------------------------------

### Get a project variable with a specific scope

Source: https://docs.gitlab.com/cli/variable/get

Fetches a variable's value for a particular environment scope within a project.

```bash
glab variable get -s SCOPE VAR_KEY
```

--------------------------------

### Get Secure File Details by ID

Source: https://docs.gitlab.com/cli/securefile/get

Retrieves the details of a secure file identified by its numeric ID in the current project.

```console
glab securefile get 1
```

--------------------------------

### Show help for state lock command

Source: https://docs.gitlab.com/cli/opentofu/state/lock

Displays help information for the `glab opentofu state lock` command.

```bash
glab opentofu state lock --help
```

--------------------------------

### Open Project in Web Browser

Source: https://docs.gitlab.com/cli/repo/view

Use the `-w` or `--web` flag to open the project's page in the default web browser.

```console
glab repo view -w
```

--------------------------------

### Login with Token from File

Source: https://docs.gitlab.com/cli/auth/login

Authenticates against a GitLab instance by reading an access token from a file via standard input.

```bash
glab auth login --stdin < myaccesstoken.txt
```

--------------------------------

### Update GitLab Duo CLI Binary

Source: https://docs.gitlab.com/cli/duo/cli

Check for and install updates to the Duo CLI binary using the `--update` flag.

```bash
# Check for and install updates
glab duo cli --update
```

--------------------------------

### Upload a file to a project wiki

Source: https://docs.gitlab.com/cli/api

Uploads a file to a project wiki using a POST request with form data. Includes the file and branch name.

```bash
glab api --method POST projects/:fullpath/wikis/attachments --form "file=@./image.png" --form "branch=main"
```

--------------------------------

### Get Label Info from Another Project

Source: https://docs.gitlab.com/cli/label/get

Retrieves information for a specific label from a different project by specifying the repository owner and name.

```bash
glab label get 1234 -R owner/repo
```

--------------------------------

### Show the full schema (compact, no node detail)

Source: https://docs.gitlab.com/cli/orbit/remote/schema

Use this command to display the entire GitLab Knowledge Graph ontology in a compact JSON format without detailed node information.

```console
glab orbit remote schema
```

--------------------------------

### Select Another Repository

Source: https://docs.gitlab.com/cli/issue/view

Select a different repository to view the issue from, using various formats like OWNER/REPO or a full URL.

```bash
glab issue view -R NAMESPACE/REPO 123
```

--------------------------------

### Show help for glab cluster agent token-cache

Source: https://docs.gitlab.com/cli/cluster/agent/token-cache

Displays help information for the `glab cluster agent token-cache` command and its parent commands. Use this to understand available options and subcommands.

```bash
glab cluster agent token-cache --help
```

--------------------------------

### Look up indexing progress by namespace ID

Source: https://docs.gitlab.com/cli/orbit/remote/graph-status

Use this example to check the indexing status of a namespace (group) by providing its numeric ID.

```bash
$ glab orbit remote graph-status --namespace-id 9970
```

--------------------------------

### Add Deploy Key from File with Push Permissions

Source: https://docs.gitlab.com/cli/deploy-key/add

Uploads a deploy key from a specified file and enables push permissions for it. The `--can-push` flag is set to `true`.

```console
# Read deploy key from specified key file, upload and set "can push" attribute.
glab deploy-key add ~/.ssh/id_ed25519.pub -t "my title" --can-push true
```

--------------------------------

### Add a note to an incident with a message

Source: https://docs.gitlab.com/cli/incident/note

Example of using `glab incident note` with the `--message` flag to provide a direct comment.

```bash
glab incident note 123 --message "Looking into this now."
```

--------------------------------

### Get Runner Controller Details

Source: https://docs.gitlab.com/cli/runner-controller/get

Retrieves details of a specific runner controller using its ID. This command is experimental and intended for administrator use.

```bash
glab runner-controller get 42
```

--------------------------------

### glab repo search Command Synopsis

Source: https://docs.gitlab.com/cli/repo/search

This is the basic command structure for searching repositories. Use flags like `--search` and `--output` to refine your search.

```bash
glab repo search [flags]
```

--------------------------------

### List managers as JSON

Source: https://docs.gitlab.com/cli/runner/managers

To get the output in JSON format, use the `--output json` flag. This is useful for programmatic processing of the results.

```bash
glab runner managers 1 --output json
```

--------------------------------

### Get a token for agent 123

Source: https://docs.gitlab.com/cli/cluster/agent/get-token

Use this command to retrieve a token for a specific GitLab Agent ID. Ensure you have the agent ID available.

```bash
glab cluster agent get-token --agent 123
```

--------------------------------

### Show Help for ssh-key Command

Source: https://docs.gitlab.com/cli/ssh-key

Displays help information for the `glab ssh-key` command, including available options.

```bash
glab ssh-key --help
```

--------------------------------

### Get Pipeline for Current Branch

Source: https://docs.gitlab.com/cli/ci/get

Retrieves the CI/CD pipeline details for the current branch. This is the default behavior when no specific pipeline identifier is provided.

```console
glab ci get
```

--------------------------------

### List access tokens for a specific project

Source: https://docs.gitlab.com/cli/token/list

Use this command to list access tokens for a specified project using the `--repo` flag. The project can be identified by its owner and repository name, or a group/namespace/repository path.

```console
glab token list --repo user/my-repo
```

--------------------------------

### Filter Incidents by Milestone and Status

Source: https://docs.gitlab.com/cli/incident/list

Filters incidents by a specific milestone and status. This example retrieves open incidents associated with the 'release-2.0.0' milestone.

```bash
glab incident list --milestone release-2.0.0 --opened

```

--------------------------------

### glab stack first Command Synopsis

Source: https://docs.gitlab.com/cli/stack/first

The synopsis shows the basic structure of the `glab stack first` command. Flags can be appended for additional options.

```bash
glab stack first [flags]
```

--------------------------------

### Show Help for `glab changelog`

Source: https://docs.gitlab.com/cli/changelog

Displays help information for the `glab changelog` command. This is a common option inherited from parent commands.

```bash
  -h, --help   Show help for this command.
```

--------------------------------

### Verify Orbit Reachability Only

Source: https://docs.gitlab.com/cli/orbit/setup

Use `--skip-skill` and `--skip-local` flags to perform only the reachability check without installing the skill or local CLI.

```bash
glab orbit setup --skip-skill --skip-local
```

--------------------------------

### View Project Information by Name or Path

Source: https://docs.gitlab.com/cli/repo/view

View project information for a specified repository by its name, path, or group/namespace/repo structure.

```console
# glab repo view my-project
glab repo view user/repo
glab repo view group/namespace/repo
```

--------------------------------

### Create a release with assets specified as JSON

Source: https://docs.gitlab.com/cli/release/create

Define release assets, including their name, URL, type, and direct file path, using a JSON string.

```console
glab release create v1.0.1 --assets-links='
[
  {
    "name": "Asset1",
    "url":"https://<domain>/some/location/1",
    "link_type": "other",
    "direct_asset_path": "path/to/file"
  }
]'
```

--------------------------------

### Verify Attestation for Filename in Project

Source: https://docs.gitlab.com/cli/attestation/verify

Use this command to verify the attestation for a specific file within a GitLab project. Ensure you have the cosign binary installed.

```console
glab attestation verify gitlab-org/gitlab filename.txt
```

--------------------------------

### List current project's access tokens

Source: https://docs.gitlab.com/cli/token/list

Use this command to list access tokens for the current project. The default output format is text.

```console
glab token list
```

--------------------------------

### Get Runner Controller Details as JSON

Source: https://docs.gitlab.com/cli/runner-controller/get

Retrieves details of a specific runner controller and formats the output as JSON. This is useful for programmatic access or further processing.

```bash
glab runner-controller get 42 --output json
```

--------------------------------

### Get Deploy Key for a Specific Repository

Source: https://docs.gitlab.com/cli/deploy-key/get

Retrieves a deploy key from a repository other than the current one by specifying the repository using the `--repo` flag.

```bash
glab deploy-key get 1234 --repo owner/repo
```

--------------------------------

### Add Deploy Key from Stdin

Source: https://docs.gitlab.com/cli/deploy-key/add

Uploads a deploy key by reading it from standard input. Requires the `--title` flag.

```console
# Read deploy key from stdin and upload.
glab deploy-key add -t "my title"
```