glab-incident

glab incident

Overview


  Work with GitLab incidents.                                                                                           
         
  USAGE  
         
    glab incident [command] [--flags]  
            
  EXAMPLES  
            
    $ glab incident list               
            
  COMMANDS

close [<id> | <url>] [--flags]   Close an incident.
list [--flags]                   List project incidents.
note <incident-id> [--flags]     Comment on an incident in GitLab.
reopen [<id> | <url>] [--flags]  Reopen a resolved incident.
subscribe <id>                   Subscribe to an incident.
unsubscribe <id>                 Unsubscribe from an incident.
view <id> [--flags]              Display the title, body, and other information about an incident.

FLAGS

-h --help                        Show help for this command.
-R --repo                        Select another repository. Can use either `OWNER/REPO` or `GROUP/NAMESPACE/REPO` format. Also accepts full URL or Git URL.


## Quick start

```bash
glab incident --help

# Comment with a local attachment
glab incident note 123 --message "Current dashboard state" --attach ./dashboard.png

glab incident list validates both output selectors before making the request: --output accepts only text or json, while --output-format accepts only details, ids, or urls. The two selectors are mutually exclusive. Treat an immediate “must be one of” error as invalid local input rather than a GitLab API failure.

Attach files to incident comments

The experimental --attach <path> flag uploads a file to the incident's project and appends the returned Markdown reference to the comment. Repeat it for multiple files. An attachment can be the entire comment and skips the editor; --attach - reads the attachment from standard input.

Subcommands

See references/commands.md for full --help output.

About this skill

Overview

Attach files to incident comments

Subcommands