glab(1)

💅 glab-incident — your incident-handling bestie

okay so real talk, this is the glab manpage for the incident command, and honestly? it's giving "I keep your services from spiraling" energy. welcome to the group chat 🫶

---

✨ NAME ✨

glab-incident — work with GitLab incidents, bestie. that's the whole vibe.

---

🦋 SYNOPSIS 🦋

glab incident [command] [flags]

---

🌸 DESCRIPTION 🌸

okay so picture this: something breaks in prod 😭 and you need a paper trail for the chaos. that's what incidents are for, no cap — incidents track service disruptions and their resolution. like, the whole arc: the thing broke, and then the thing got fixed.

with this command you can:

• list and view incidents 👀
• comment on them 💬
• subscribe to them 🔔
• close them ✅
• or reopen them 🔓

and if you're not even in the right repo? use --repo to target a project other than the current one. main character move, fr fr.

---

💅 OPTIONS 💅

• -R, --repo="" — select another repository. you can hit it with OWNER/REPO or GROUP/NAMESPACE/REPO, and bestie, the full URL or a Git URL is also accepted. flexible icon behavior ✨

---

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

• -h, --help[=false] — show help for this command. your little escape hatch, lowkey essential 🌈

---

🎀 EXAMPLE 🎀

glab incident list

that's it. that's the whole starter pack. go off 👑

---

🔥 SEE ALSO 🔥

• glab(1)
• glab-incident-close(1)
• glab-incident-list(1)
• glab-incident-note(1)
• glab-incident-reopen(1)
• glab-incident-subscribe(1)
• glab-incident-unsubscribe(1)
• glab-incident-view(1)

---

ngl, quick heads up: this one is auto generated by spf13/cobra, dated Nov 2026, and it belongs to the glab(1) family. so if something looks a little machine-written, that's why 💀

k that's the page!! go close some incidents, you absolute legend 💖🦋