GCLI-LABELS(1)

πŸ“¦
version 2.13.0 Β· 5 versions
, in nixpkgs unstable, ubuntu stonking

🏷️ GCLI-LABELS β€” the manual page, bestie edition πŸ’…

okay so this is gcli labels, a page from the General Commands Manual section 1, and it's literally all about managing ticket labels in git forges. sit down, grab a boba, we're doing this ✨


✨ NAME ✨

gcli labels β€” manage ticket labels in git forges πŸŽ€


🌸 SYNOPSIS 🌸

gcli labels [forge-path] [-o owner -r repo]
gcli labels [forge-path] create [-o owner -r repo] -d description -n
            name -c colour
gcli labels [-o owner -r repo] -i name actions...

πŸ¦‹ DESCRIPTION πŸ¦‹

Use gcli labels to list, create, edit or delete labels for Pull Requests / Merge Requests and issues in repositories across various git forges β€” think GitHub, GitLab and Gitea. no cap, it does all of them πŸ’–

If you don't specify any action at all? It just lists every label defined in the given or auto-detected repository. the way it's giving "I got you" energy fr fr πŸ‘‘


πŸ’œ OPTIONS πŸ’œ

  • -o, --owner owner β€” work in the repository of the given owner. 🫢 heads up: this one can only be used together with -r. they're a package deal, bestie.
  • -r, --repo repo β€” work in the given *repo*sitory. same deal β€” this can only be used in combination with -o. no solo flights πŸ™ˆ
  • -i, --name name β€” execute actions on the label identified by name. this is how you aim your little label-tool at one specific label 🎯

🌈 SUBCOMMANDS 🌈

create

Creates a new label in the given or auto-detected repository. so iconic of it ✨

The following flags must be specified β€” like, required required, not optional-suggestion core:

  • -n, --name name β€” set the short name of the label to the given name.
  • -d, --description description β€” set the description of the label to the given text. ⚠️ note that on GitHub this field may only consist of up to 150 characters. 150. that's it. that's the limit. plan your yapping accordingly 😭
  • -c, --colour code β€” set the colour of the label to the given code. code is expected to be a 6 digit hexadecimal RGB colour code. six digits, hex, RGB, periodt πŸ’…

πŸŽ€ ACTIONS πŸŽ€

When you give a specific label with -i, you can execute one or more of the following actions. stack 'em, bestie 🫢

  • status β€” print a short summary about the label. the vibe check 🧚
  • name new-name β€” change the name of the label to the given new-name. (glow-up arc activated πŸ’–)
  • description new-description β€” change the description of the label to new-description. if it has spaces in it, wrap it in quotes, or the shell will do that thing where it splits everything and ruins your whole day 😭
  • colour hexcolour β€” change the colour of the label to the six-digit hexadecimal RGB colour code hexcolour. main character energy, in hex 🎨
  • delete β€” delete the given label. bye bye πŸ‘‹ (and yeah, peep the BUGS section down there, it's got opinions about this one)

⭐ EXAMPLES ⭐

Print a list of all labels in the current project:

$ gcli labels

Create a new label called 'bug' with a description 'Something is not working as expected' and give it a red colour:

$ gcli labels create \
                --name bug \
                --description "Something is not working as expected" \
                --colour FF0000

Delete the label 'foobar' in herrhotzenplotz/gcli and use the configured account 'gitlab':

$ gcli -a gitlab labels -o herrhotzenplotz -r gcli -i foobar delete

List labels in herrhotzenplotz/gcli on GitLab using the forge path shorthand:

$ gcli labels gl:herrhotzenplotz/gcli

no notes. absolutely ate πŸ”₯


🌈 SEE ALSO 🌈

git(1), gcli(1) β€” go read those too, bestie, iykyk πŸ“š


πŸ‘‘ AUTHORS πŸ‘‘

Nico Sonack aka. herrhotzenplotz <nsonack@herrhotzenplotz.de> and contributors. legends, all of them 🫢✨


πŸ’€ BUGS πŸ’€

so the delete subcommand should ask for confirmation and have a flag to override this behaviour. it currently does not. noted, filed, living in this manpage rent-free 🫠

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 to use the mailing list. so like… mailing list first, mwah πŸ’‹


fr fr, this page is from gcli version 2.13.0, dated 05-Aug-2026 β€” that's the whole footer, bestie. take care, hydrate, and tag your labels πŸ’œπŸ¦‹πŸŒΈ
πŸ“¦ where this page comes from