GCLI-FORKS(1)

💖 GCLI-FORKS(1) 💖

okay bestie, so this is a page from the General Commands Manual — it's gcli forks, one of the lil' commands that lives inside gcli. pull up a chair 🪑✨

---

🌸 NAME 🌸

gcli forks — manage repository forks in git forges. yeah. forking. like the lizard but for repos 🦎

---

✨ SYNOPSIS ✨

gcli forks [forge-path] [-n n] [-y] [-s] [-o owner -r repo] actions...
gcli forks [forge-path] create [-o owner -r repo] [-i target-owner]

two whole shapes, bestie. pick your fighter 💅

---

🦋 DESCRIPTION 🦋

so like — you use gcli forks to manage forks of other repositories across all the various git(1) forges out there, y'know, GitHub, GitLab, Gitea, the whole squad 👑 no cap, it's giving "I don't wanna open a browser" energy and honestly? iconic.

---

🎀 OPTIONS 🎀

• -o, --owner _owner_ — operate on the repository belonging to this _owner_. heads up though: this one only works in combination with -r. they're a package deal, fr fr 🫶
• -r, --repo _repo_ — operate on the given _repo_. and same vibe: only valid in combination with -o. you cannot have one without the other, it's giving soulmates 💜
• -y, --yes — do not ask for confirmation. assume yes. it just goes. no questions, no takebacks 😭
• -s, --sorted — reverse the output so that the most recent items appear at the bottom. yes it's backwards, yes that's the point, live a little ✨
• -i, --into _target-owner_ — when you're forking a repository, this is the organisation or user that the repo gets forked into. so like, where's it going. destination vibes 🧚
• -n, --count _n_ — fetch at least _n_ forks. and if you set _n_ to -1?? it fetches all of them. all of them. every single one 🌈

Default: 30. lowkey important warning though bestie — on repositories with many forks, fetching all forks can take a considerable amount of time and may result in rate limiting by the respective API. so like, don't just yolo -1 on a mega-repo unless you're prepared to sit there 💀

---

🌟 ACTIONS 🌟

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

🍓 delete

delete the fork. you'll be asked for confirmation unless you set -y. (bold move skipping that, but slay I guess 💅)

the following flags can be specified:

• -r, --repo — see “OPTIONS” 👀
• -o, --owner — see “OPTIONS” 👀
• -y, --yes — do not ask for confirmation before deleting the fork. see “OPTIONS”. it's giving "I know what I'm doing" energy ✨

---

💫 EXAMPLES 💫

clone vim/vim and fork it into your account:

$ git clone git@github.com:vim/vim
$ cd vim
$ gcli forks create --into <myaccount>

this will ask you if you want to add a remote to your fork. in case you accept the offer, the origin remote will be renamed to upstream and a new origin will be pointed at your newly created fork. (glow up moment honestly 🫶) you may also want to setup a .gcli file at the same time:

$ printf -- "pr.upstream=vim/vim\npr.base=trunk\n" >> .gcli

delete your fork of the current repository without confirmation:

$ gcli forks -y delete

list forks of herrhotzenplotz/gcli on GitHub using the forge path shorthand:

$ gcli forks gh:herrhotzenplotz/gcli

---

👑 SEE ALSO 👑

git(1), gcli(1)

---

💜 AUTHORS 💜

Nico Sonack aka. herrhotzenplotz <nsonack@herrhotzenplotz.de> and contributors. (contributors!! we love a collective effort 🫶)

---

🙈 BUGS 🙈

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.

but ngl, the preferred and quickest method is to use the mailing list ✨ don't make the maintainers wait bestie 💖

---

and that's the whole page! 🌸 this was gcli version 2.13.0, dated 05-Aug-2026, and it originally lived as page GCLI-FORKS(1) in the General Commands Manual. mwah 💅✨