A gist <c>reate/<r>ead/<u>pdate/<d>elete (crud) utility(pronounced as Keg). sounds boring? let me try again: it's a command-line snippet (being called a gist in github's terminology) manager .it can perform all the operations,you would want to perform on a gist.this includes:
- Creating gist(s).
- Modifying existing gist(s).
- Downloading gist(s). [1]_
- Listing public/secret gists for authenticated users as well as for unauthenticated users(only public).
- Deleting gist(s).
- Creating a local backup of all the gists(for authenticated users).
ceg can also be used as a library. check out Api documentation.
| [1] | As of now, only files smaller than 10MB can be downloaded as allowed by GitHub API.this is planned to change once "git clone" has been implemented internally in future releases. |
The simplest way to install ceg with battery included is by using pip:
# py instead of python3 on windows # Please be sure to use the -U tag to install # the latest version as builds are automatically done at github # and all patches are pushed to new releases. python3 -m pip install -U ceg
You can also use pipx if you plan to only use ceg as a command line tool.pipx ensures dependency isolation and is made specifically for cli tools. but please be aware that you will not be able to use ceg as a library if installed from pipx since its installed in a virtenv.
python3 -m pipx install --system-site-packages ceg
You can also install ceg manually. for that, you need to have poetry installed and be on a system with a minimal python version being 3.7 (one thing to keep in mind is that i am using python 3.10 so you will need to change python version in pyproject.yaml to your version and build it with that).after installing poetry, you can just do poetry build and pip install from dist/ceg*.whl or whatever you prefer. however please be mindful that installing poetry from pip is not recommended.
# you can also use install/uninstall scripts after cloning the repo, if on *nix. curl -sSL https://install.python-poetry.org | python3 - git clone https://github.com/justaus3r/ceg.git cd ceg poetry install poetry build
After installation, you can optionally set an environment variable named GITHUB_SECRET_KEY and save your GitHub secret there. this helps to preclude you from passing your key explicitly every time you use the utility. however, if you don't feel comfortable storing it in an environment variable, you can use -sk/--secret-key and pass it to the utility.
usage: ceg [options] [sub-arguments]
An all in one github's gist manager.
options:
-h, --help show this help message and exit
-po GISTNAME [GISTNAME ...], --post GISTNAME [GISTNAME ...]
create a gist
-pa GISTNAME [GISTNAME ...], --patch GISTNAME [GISTNAME ...]
modify an existing gist
-g GISTID [GISTID ...], --get GISTID [GISTID ...]
download gist(s)
-d GISTID [GISTID ...], --delete GISTID [GISTID ...]
remove gist(s)
-l [OPT-USERNAME], --list [OPT-USERNAME]
list public/private gists for a user
-bk [OPT-USERNAME], --backup [OPT-USERNAME]
create a backup of all gists
-sk SECRETKEY, --secret-key SECRETKEY
user's github secret key
-nl, --no-logging don't log anything to stdout
-v, --version show utility's semantic version
sub-arguments:
--post/-po
--no-public/-np switch gist visibility to private
--description/-desc description for the gist
--patch/-pa
--gist-id/-gi gist-id for the gist
For more usage help, check out https://www.github.com/justaus3r/ceg/#examples
You can create a gist with multiple files added at the same time. but please know that if your files have a naming scheme like gistfile{number}, it will be
ignored by ceg as GitHub uses this naming scheme internally. for creating a secret gist, you can just append --no-public/-np in the argument list.
$ ceg --post "file1" "file2" -desc "This is description of the gist"
Modifying a gist is just as easier as creating a gist. just pass all the modified files to ceg and the gist-id of gist you are modifying(use --gist-id/gi).
you can also update the gist description by passing --description/-desc NEWDESCRIPTION.
# use '->' for renaming files $ ceg --patch "file1->file1_renamed" "file2" -desc "My dirty secrets." -gi abcdef
From v0.4.0 ownwards your files doesn't have to be in running directory of ceg, i.e: you can use files from other directories by giving their path.
You can list all of your gists, which will be beautified before printing to stdout. please note that if you are not authenticated(not giving GitHub secret key) then you can use --list-other/-lo but you will only be shown public gists. [1]_
$ ceg -l # or ceg -lo "Justaus3r" # 0.5.0 ownwards $ ceg -l "user:Justaus3r"
| [1] | This syntax has been changed ownwards 0.5.0. |
You can download an arbitrary amount of gists in one go! just pass their gist-id, sit back and let the magic happen! all of the gists will be downloaded in directories named with their respective gist-ids.
$ ceg -g gistid1 gistid2 gistid3 # or(0.5.0 ownwards) ceg -g "user:Justaus3r" gistid1 gistid2
Note: changed in 0.5.0. now unauthenticated users can also download gists(public only).
You can delete multiple gists by simpling passing their gist-id.
$ ceg -d gistid1 gistid2
All user gists can be backed up, only by using a single command.
$ ceg -bk # or (0.5.0 ownwards) ceg -bk "user:Justaus3r"
All operations can be performed under the silent mode, under which the logger is turned off and nothing(including errors) is printed to stdout.
$ ceg -l -nl
Is ceg not your taste? well then you can try following similar projects:
You can report all issues/feature requests at GitHub bug tracker.
All kinds of contributions are welcomed. though please be mindful that this project is statically typed and uses black formatting so please type-check(using mypy) before a PR. I haven't yet added py.typed, nor is the project type-checked at installation or any workflows setup to do so (now we actually do type checking using workflow) because I am too lazy. tho I plan to do that. also, note that
conventional commits and semantic versioning are used for git commits/versioning.
if you like the project, you can show appreciation by giving it a star.
This project is distributed under "GNU General Public License v3.0",and can be distributed with its later versions.