glab(1)

πŸ’… glab(1) β€” the glab-issue-note page, bestie edition πŸŽ€

okay so you opened the manual for glab-issue-note, which is the glab subcommand that lets you comment on an issue in GitLab. she's a little icon, she's a little legend, and honestly she's about to be your new fave. let's get into it ✨


🌸 NAME 🌸

glab-issue-note β€” literally just: comment on an issue in GitLab. that's the whole gig fr fr πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

glab issue note  [flags]

(yes there's a double space in there, no I will not be fixing it, it's part of the lore πŸ’€)


✨ DESCRIPTION ✨

okay so here's the vibe check πŸ‘‘

If you don't pass --message, glab opens up an editor β€” but only at a terminal. Otherwise (like when input is piped in or redirected), it just reads the comment straight from standard input. so like, both paths are valid, it just depends on how you're feeding her 🫢

--attach uploads a file and then references it at the end of the comment. want more than one file? repeat the flag, bestie, go off πŸ’…. or pass - to read the file from standard input. and here's the little detail that matters: an attachment is content on its own, so a comment with only --attach neither prompts nor reads a body from standard input. it just... attaches. no body, no editor, no stdin, periodt βœ‹

⚠️ experiment alert, no cap: the --attach flag is an experiment. it might be unstable, it might get removed at any time, and it is not ready for production use. you've been warned, bestie 😭 for more info, see https://docs.gitlab.com/policy/development_stages_support/.

πŸŽ€ 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. multiple files!! she's versatile πŸ’…
  • --internal[=false] β€” create the note as an internal note, visible only to project members. secret girl business 🀫
  • -m, --message="" β€” the message text. your actual words, iconic 🌟

πŸ’œ OPTIONS INHERITED FROM PARENT COMMANDS πŸ’œ

  • -h, --help[=false] β€” show help for this command. when in doubt, ask for help, it's giving self-care 🧚
  • -R, --repo="" β€” select another repository. you can use either OWNER/REPO or GROUP/NAMESPACE/REPO. the full URL or Git URL is also accepted. flexible queen 🌈

πŸ”₯ EXAMPLE πŸ”₯

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

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

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

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

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

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

look at all those options, she ate and left no crumbs πŸ“


πŸ‘‘ SEE ALSO πŸ‘‘

  • glab-issue(1) β€” the parent command, go say hi to her too 🫢

okay that's the whole page, you're basically a glab issue note expert now πŸ’– one last thing for the receipts: this page is auto generated by spf13/cobra, version date Nov 2026, and it lives under the manual name glab(1). mwah, go comment on some issues, main character πŸŒŸπŸ’…βœ¨

πŸ“¦ where this page comes from