GCLI-REPOS(1)

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

πŸ’– GCLI-REPOS(1) β€” the repos page, bestie edition πŸ’–

General Commands Manual ✨ welcome to the corner of the manual where you get to boss your git forges around. It's giving main character energy, fr fr.


🌸 NAME 🌸

gcli repos β€” manage remote repositories on various git forges πŸ¦‹


✨ SYNOPSIS ✨

gcli repos [-s] [-n n] [-o owner] [search-terms...]
gcli repos create -r name [-d description] [-p]
gcli repos -o owner -r repo actions...

πŸ’… DESCRIPTION πŸ’…

okay so gcli repos is your lil bestie for listing, searching, and managing repositories β€” either your own or an organisation's β€” on git(1) forges like GitHub, Gitea and GitLab. iconic behaviour honestly.

If you give it no actions, gcli repos just lists repositories. Whose? The ones belonging to the owner you passed with -o, or β€” if you didn't pass -o at all β€” your own. simple as that πŸ’–

When you've specified search-terms..., it doesn't list anymore, it searches instead. Wanna keep the search locked to one specific owner? That's what -o owner is for. πŸ”

And when you've got both an owner and a repository specified, the actions... you gave it get executed on that repository. Go read β€œACTIONS” for the tea. πŸ‘‘


πŸŽ€ OPTIONS πŸŽ€

  • -s, --sorted β€” flips the output around, so the most recent items show up at the bottom instead of the top. reverse-chronological slay. πŸ™ƒ
  • -o, --owner owner β€” operate on the repository belonging to this owner. ⚠️ This option can only be used in combination with -r.
  • -r, --repo repo β€” operate on the given repo. ⚠️ This option can only be used in combination with -o... unless you're creating a repository. special little exception, she's built different. πŸ’…
  • -y, --yes β€” don't ask for confirmation, just assume yes. Applies only to the delete action. no take-backsies energy. 😭
  • -n, --count n β€” fetch at least n repositories. Set n to -1 and it'll fetch all of them. Default: 30. > careful bestie: on owners with a whole lotta repos, fetching all of them can take a considerable amount of time and may result in rate limiting by the GitHub/GitLab API. πŸ’€
  • -d, --description description β€” set the description of a repo you're about to create. πŸ“
  • -p, --private β€” create a private repo. 🀫

πŸ‘‘ ACTIONS πŸ‘‘

actions... may be one or more of the following:

  • delete [-y] β€” delete the repository. You'll be asked for confirmation unless you set -y. πŸ’€
  • set-visibility level β€” change the visibility level of the repository. level may be one of:
    • private β€” make the repository private. πŸ™ˆ
    • public β€” make the repository public. πŸ“£

🌈 EXAMPLES 🌈

List your own repos:

$ gcli repos

List neutaaaaan's repositories:

$ gcli repos -o neutaaaaan

Delete vim/vim without confirmation:

$ gcli repos -o vim -r vim -y delete

Create a repository called emacs with a description and make it public:

$ gcli repos create -r emacs -d "welcome to the holy church of emacs."

🫢 SEE ALSO 🫢

git(1), gcli(1), emacs(1)


πŸ’œ AUTHORS πŸ’œ

Nico Sonack aka. herrhotzenplotz <nsonack@herrhotzenplotz.de> and contributors. πŸŽ€


πŸ› BUGS πŸ›

Currently it is only possible to create repositories for authenticated users, so it's impossible to create a repository in another organisations. 😭

The Gitea backend doesn't yet support searching repositories of a given user:

$ gcli repos -o herrhotzenplotz foobar

This will error out indicating that this is not supported by gcli. πŸ’€

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 β€” and this is the important part β€” the preferred and quickest method is to use the mailing list. ✨


and that's the whole page, bestie πŸ¦‹ this was gcli version 2.13.0, dated 05-Aug-2026. periodt. πŸ’…

πŸ“¦ where this page comes from