glab(1)

💅 glab-incident-note — aka the glab(1) manual, incident-comment edition 🎀

Hey bestie, welcome to the glow-up of the glab manual page. This particular slice of it is all about glab-incident-note, and yes it's exactly as iconic as it sounds: you're dropping a comment on an incident in GitLab, and doing it with style. 🦋

✨ NAME ✨

glab-incident-note — comment on an incident in GitLab. Periodt. 💖

🌸 SYNOPSIS 🌸

glab incident note  [flags]

🧚 DESCRIPTION 🧚

Okay so here's the vibe check. If you don't pass --message, it opens up an editor for you at a terminal — very "write your feelings in a text box" energy 😌. Otherwise (like when your input is piped or redirected), it just reads the comment from standard input. No editor, no drama.

Now, --attach uploads a file and references it at the end of the comment — like a little hyperlink garnish on your note. 🎀 Repeat the flag if you've got more than one file, or pass - to read the file from standard input. And listen: an attachment is content on its own, so a comment that has only --attach neither prompts nor reads a body from standard input. It just… is. Main character attachment energy. 👑

⚠️ Heads up bestie: the --attach flag is an experiment. It might be unstable, or get removed at any time, and it is not ready for production use. Fr fr, do not build your whole workflow on it. More info lives at https://docs.gitlab.com/policy/development_stages_support/ — go read it, iykyk. 💀

⭐ OPTIONS ⭐

• --attach=[] — (EXPERIMENTAL) upload a file and reference it at the end of the comment. Use - to read the file from standard input. Repeat the flag to attach multiple files. 🍓
• --internal[=false] — create the note as an internal note, visible only to project members. Secret lil note, just for the group chat. 🙈
• -m, --message="" — the message text. Your words, your moment. ✨

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

• -h, --help[=false] — show help for this command. When in doubt, ask the manpage. 🫶
• -R, --repo="" — select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted. So many options, all slay. 💜

🔥 EXAMPLE 🔥

# Comment on incident 123, opening an editor for the message
glab incident note 123

# Comment with the message given inline
glab incident note 123 --message "Looking into this now."

# Create an internal note, visible only to project members
glab incident note 123 --message "Rotating the leaked token now." --internal

# Attach a screenshot alongside the message
glab incident note 123 --message "Here is the repro." --attach ./screenshot.png

# Attach an image piped from the clipboard
pngpaste - | glab incident note 123 --attach -

# Comment with the message read from a file
glab incident note 123 < comment.md

Look at those examples. Ate, honestly. 💅

💖 SEE ALSO 💖

glab-incident(1) — the parent command, the origin story, the blueprint. Go say hi. 🌸

---

And that's a wrap, bestie! This lil page was auto generated by spf13/cobra, dated Nov 2026, and it belongs to the glab(1) manual fam. Now go comment on that incident like the Unix icon you are. 👑🎀✨