GCLI-GISTS(1)

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

πŸ’– GCLI-GISTS β€” the girlies' guide to gcli gists πŸ’–

okay so bestie, this is section 1 of the manual, and it's all about gcli gists β€” the command that manages your GitHub Gists. yes, the whole thing, listed, made, grabbed, deleted. let's get into it 🫢


✨ NAME ✨

gcli gists β€” manage GitHub Gists πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

gcli gists [-s] [-l] [-n n] [-u user]
gcli gists create [-d description] [-f path] gist-file-name
gcli gists delete [-y] gist-id
gcli gists get gist-id file-name

πŸ¦‹ DESCRIPTION πŸ¦‹

Use gcli gists to list, create, download or delete GitHub Gists. that's the whole vibe, four jobs, one command, iconic.

Without a subcommand specified, gcli gists will list the Gists of the given β€” or auto-detected β€” user account. so if you just type it and hit enter, it's gonna snoop around and figure out whose gists you mean. lowkey smart of it fr fr.


🌸 OPTIONS 🌸

these are the top-level options, bestie, the ones for when you're just listing:

  • -l, --long β€” print a long list instead of a short table. more deets, more rows, more to look at πŸ‘€
  • -s, --sorted β€” reverse the output so the most recent items appear at the bottom instead of the top. yes, it flips it like that.
  • -u, --user owner β€” list the Gists belonging to the given user. you point, it fetches.
  • -n, --count n β€” fetch at least n gists. setting n to -1 will fetch all gists. default: 30.
⚠️ heads up bestie: on users with many gists, fetching all gists can take a considerable amount of time and may result in rate limiting by the GitHub API. so like… maybe don't just yolo -1 on a legend's account. 😭

πŸ‘‘ SUBCOMMANDS πŸ‘‘

🌈 create 🌈

Paste a new Gist. the following flags can be specified:

  • -f, --file file β€” read the content from the specified file instead of standard input. no piping required, she takes a path πŸ’…
  • -d, --description description β€” the description of the Gist to be created. give your gist a little blurb, a lil name tag.

πŸ“ delete πŸ“

Delete a Gist. the following options can be specified:

  • -y, --yes β€” do not ask for confirmation before deleting the Gist. assume yes. this one is the "no take-backsies, just do it" flag. use it with care, bestie.

🧚 get 🧚

Download a file from a Gist. there are no options to this subcommand. it's just built different (simple). periodt.


⭐ EXAMPLES ⭐

List neutaaaaan's Gists:

$ gcli gists -u neutaaaaan

Paste a new gist named foobar and read from foobar.txt:

$ gcli gists create foobar < foobar.txt

Delete gist with id 3b546069d2856e6051bbe3c1080f1b5d:

$ gcli gists delete 3b546069d2856e6051bbe3c1080f1b5d

Print foobar.txt from Gist with id 3b546069d2856e6051bbe3c1080f1b5d into your pager:

$ gcli gists get 3b546069d2856e6051bbe3c1080f1b5d foobar.txt | $PAGER

πŸ”₯ SEE ALSO πŸ”₯

git(1), gcli(1) β€” go read those too, they're the supporting cast 🫢


πŸ’œ AUTHORS πŸ’œ

Nico Sonack aka. herrhotzenplotz <nsonack@herrhotzenplotz.de> and contributors. absolute legends. main character energy, no cap. πŸ‘‘


πŸ’€ BUGS πŸ’€

This subcommand only works on GitHub. it is not implemented for GitLab, as GitLab snippets work differently. so like, don't come for it, it simply doesn't do that. πŸ™ˆ

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. iykyk. ✨


πŸŽ€ and that's the whole page bestie!! this was gcli gists, from gcli 2.13.0, dated 05-Aug-2026. go forth and gist responsibly πŸ’…πŸ’–βœ¨
πŸ“¦ where this page comes from