GCLI-ISSUES(1)

📦
version 2.13.0 · 5 versions
, in nixpkgs unstable, ubuntu stonking

💖 GCLI-ISSUES 💖

okay bestie so this is the GCLI-ISSUES(1) page from the General Commands Manual and it's literally your ✨guide✨ to making gcli handle all your issues for you. yes. issues. the bug kind. not the emotional kind (that's a different manpage, and it's therapy). 🎀

✨ NAME ✨

gcli issues — manage issues across all your various git forges 🌈

🌸 SYNOPSIS 🌸

gcli issues [forge-path] [-n n] [-a] [-s] [-A author] [-L label]
            [-M milestone] [-S assignee] [-o owner -r repo]
            [search-query]
gcli issues [forge-path] -i issue [-o owner -r repo] actions...
gcli issues [forge-path] create [-o owner -r repo] [-y]
            [-T template-file] [issue-title]

no cap, that's the whole vibe right there 💅

🦋 DESCRIPTION 🦋

sooo gcli issues is your girl for searching, listing, creating, editing, or deleting issues in repos across a bunch of different git(1) forges — think GitHub, GitLab, Gitea, the whole lineup 👑

If you don't specify any action at all, gcli issues will just... list the issues in the repo you gave it, or in the one it auto-detected all by itself. main character energy fr fr 🫶

and hiii if you're on Bugzilla you can drop the quick-search syntax right into the search-query to get way more fine-grained with your searching ✨ go check “SEE ALSO” and “EXAMPLES” below, i got you 💖

💅 OPTIONS 💅

  • -s, --sorted — flips the output around so the most recent stuff ends up at the bottom instead of the top 🔄
  • -o, --owner owner — list issues in the repo belonging to this owner. ⚠️ this one only works if you also pass -r, they're a package deal bestie
  • -r, --repo repo — list issues in this repo. ⚠️ and this one only works alongside -o. again: package deal 🤝
  • -a — list issues disregarding their state, meaning closed ones show up too. cannot be combined with actions. (also it does not touch the -n option, leave -n alone she's fine) 🚫
  • -A, --author user — only show issues written by this user ✍️
  • -L, --label label — filter by this label. ⚠️ you may only specify this once. once. uno. 1️⃣
  • -M, --milestone milestone — filter by this milestone. ⚠️ also once only!
  • -S, --assignee assignee — filter by this assignee. ⚠️ also also once only!!
  • -n, --count n — fetch at least n issues. set n to -1 and you get all of them 😳 default: 30. heads up though: on big repos, fetching all the issues can take a considerable amount of time and might get you rate limited by the API. see “CAVEATS”. 🐌
  • -i, --id issue — run the given actions on this specific issue 🎯

👑 SUBCOMMANDS 👑

🌟 create

makes a brand new issue in the repo you gave or the one that got auto-detected ✨ your editor will pop open and ask you to type in an issue message, so get those thoughts ready 💭

if you leave out the issue title, gcli will interactively prompt you for every single little detail needed to create the issue. so conversational. so attentive. 🫶

the following flags can be specified:

  • -o, --owner owner — tell it who owns the repo you're creating the issue in 🏠
  • -r, --repo repository — tell it which repository the issue is getting created in 📦
  • -T, --template template-file — use this template-file as the template for the issue message body 📝
  • -y, --yes — no confirmation before creating the issue, just assume yes and GO 🏃♀️💨

🔥 ACTIONS 🔥

actions... can be one or more of these bad boys:

  • all — show both a summary and the original post of the issue 🌈
  • comments — print a list of the comments sitting under the issue 💬
  • status — print a short lil summary of the issue 📋
  • op — print the original post of the issue 📰
  • close — close the issue 🔒
  • reopen — reopen an issue that got closed 🔓
  • assign assignee — assign the issue to the given assignee (that's a user name btw) 🙋♀️
  • labels [options] — the following options can be specified more than once:
    • add label — add the given label to the issue ➕
    • remove label — remove the given label from the issue ➖
  • milestone id — assign the issue to the milestone with the given id 🏁
  • milestone -d — clear the associated milestone of the given issue 🧹
  • notes — an alias for the comments action, prints the list of comments associated with the issue 📝
  • title new-title — change the title of the issue to new-title ✏️
  • attachments — list bug attachments. ⚠️ this action is only available on Bugzilla 🐛
  • open — open the issue in a web browser using xdg-open(1) 🌐
  • edit — open the original post in an editor to edit it. after you save and exit, the original post gets updated when you confirm it ✅
  • due YYYY-mm-dd — set the issue to be due on the given date 📅

🎀 EXAMPLES 🎀

print a list of issues in the current project:

$ gcli issues

search for issues containing “crash” in contour-terminal/contour on GitHub, including closed issues:

$ gcli -t github issues -o contour-terminal -r contour -a crash

list issues in herrhotzenplotz/gcli on GitLab using the forge path shorthand:

$ gcli issues gl:herrhotzenplotz/gcli

report a new issue in the current project; interactively asking for details:

$ gcli issues create

report a new issue titled “summary here” in the current project:

$ gcli issues create "summary here"

print both a summary and comments of issue 1 in herrhotzenplotz/gcli:

$ gcli issues -o herrhotzenplotz -r gcli -i 1 status comments

add the labels ‘foo’ and ‘bar’ to the issue with id 420:

$ gcli issues -i420 labels add foo add bar

list issues with the label “bug”:

$ gcli issues -L bug

search for Bugzilla Bugs in product “foo” with “RandomUser” set in CC:

$ gcli -t bugzilla issues product:foo cc:RandomUser

🌈 SEE ALSO 🌈

git(1), gcli(1), Bugzilla QuickSearch Syntax: https://bugzilla.mozilla.org/page.cgi?id=quicksearch.html

💜 AUTHORS 💜

Nico Sonack aka. herrhotzenplotz <nsonack@herrhotzenplotz.de> and contributors. iconic behavior, thank you for your service 🫡

💀 CAVEATS 💀

GitHub and Gitea treat Pull Requests as Issues. 😭 and because of how gcli issues works semantically, the issues that are actually PRs get dropped from the output. when that happens, a note gets printed telling you how many were dropped, so you're not left wondering. and if that warning is annoying you, you can suppress it with the -q program option 🤫

🐛 BUGS 🐛

GitHub only supports removing labels from issues one by one. brutal, i know 💀 but if you still wanna remove multiple issues in a single gcli call, you can do something like this:

$ gcli issues -i42 \
        labels remove bug \
        labels remove foo

please report bugs via E-Mail to https://lists.sr.ht/~herrhotzenplotz/gcli-discuss 📧

alternatively you can report them on any of the forges linked at https://sr.ht/~herrhotzenplotz/gcli 🦋 however, the preferred and quickest method is the mailing list. periodt 💅

okay that's the whole thing, bestie — this page is from gcli 2.13.0 and it's dated 05-Aug-2026, and it lives in the GCLI-ISSUES(1) section of the manual. now go close some issues ✨🫶💖

📦 where this page comes from