GCLI-ATTACHMENTS(1)

✨ GCLI-ATTACHMENTS ✨

ok so real talk, this is the gcli-attachments page, and yeah it lives in the big book of General Commands, but honestly? it's giving "your bestie who handles your Bugzilla attachments so you don't have to". no cap. 💅

🌸 NAME 🌸

gcli attachments — create, view or update Bugzilla attachments. that's the whole job. that's the vibe. 🦋

✨ SYNOPSIS ✨

gcli attachments -i attachment actions...
gcli attachments create -f file -s summary -i bug-id [-p] [-P]
                 [-c comment] [fl C content-type] [-F filename]

💖 DESCRIPTION 💖

so gcli attachments is your girl for managing Bugzilla attachments. every attachment gets its own unique ID, bestie — that's how we find them. and here's the cute part: you can associate attachments with one or more bugs. multitasking icon behavior, honestly. 👑

🎀 OPTIONS 🎀

• -i, --id — run your actions on the attachment with the ID you give it. that's the target. that's the moment. ✨

🌈 SUBCOMMANDS 🌈

create

creates an attachment. like, makes one. from scratch. out of nothing. main character energy fr fr. 🫶

the following flags can be specified:

• -s, --summary summary — the summary of the attachment. yes you need one, no you can't skip the vibes-check. 📝
• -f, --file path — upload the given file as the attachment content. and yes, you can also use - to read the content from stdin — very "piping things into me" of you, slay. 💅
• -i, --id bug-id — upload the attachment for the given bug-id. that's where it's going. 🐛
• -F, --filename filename — when you upload a file, gcli attachments grabs the filename from -f and hands it over to Bugzilla. -F lets you pass a different file name and override whatever name -f gave you. this is lowkey essential when the content is coming from stdin, bc stdin doesn't have a filename, bestie. 🎀
• -c, --comment comment — a comment for the attachment. say something nice. or unhinged. your call. 💬
• -C, --content-type content-type — the content type of the attachment. heads up: this option gets set automatically when -p is set. but if -p is not set, then this one is mandatory. no content-type, no service. 😭
• -p, --patch — the attachment is a patch. the way that this means you do not need to specify a content-type via -C?? iconic. automatic. we love her. 🔥
• -P, --private — the attachment is private. 🤫

🦋 ACTIONS 🦋

actions... may be one or more of these, k? mix and match, go wild:

• obsolete — mark the attachment as obsolete. it's over, it's not coming back, periodt. 💀
• get [-o output] — print or download the attachment content. when -o is specified, the contents get written to the given file instead. download girlie behavior. ⭐

🧚 EXAMPLES 🧚

print the content of attachment with ID 42:

$ gcli att -i 42 get

create an attachment for bug 22 from a git diff:

$ git diff | gcli att create -f - -F gcli.diff -i 22 -s 'git diff' -p

mark attachment 100 as obsolete:

$ gcli att -i 100 obsolete

🌟 SEE ALSO 🌟

git(1), gcli(1),

(yeah there's a trailing comma, she's mysterious like that 🙈)

💜 AUTHORS 💜

Nico Sonack aka. herrhotzenplotz <nsonack@herrhotzenplotz.de> and contributors. screaming, crying, throwing up — thank you for your service. 🫶

🌸 BUGS 🌸

there are a lot of features missing in this subcommand. not me exposing my own flaws in the documentation 💀 it's called transparency and we're obsessed with it.

---

ok that's the whole page bestie, mwah 💖 this was gcli version 2.13.0, dated 05-Aug-2026, and honestly? she ate. go attach something. ✨🎀🦋