GIST(1) | Gist manual | GIST(1) |
gist - upload code to https://gist.github.com
The gist gem provides a gist command that you can use from your terminal to upload content to https://gist.github.com/.
To read a gist and print it to STDOUT
gist -r GIST_ID gist -r 374130
If you want to associate your gists with your GitHub account, you need to login with gist. It doesn´t store your username and password, it just uses them to get an OAuth2 token (with the "gist" permission).
gist-paste --login Obtaining OAuth2 access_token from github. GitHub username: ConradIrwin GitHub password: 2-factor auth code: Success! https://github.com/settings/tokens
This token is stored in ~/.gist and used for all future gisting. If you need to you can revoke it from https://github.com/settings/tokens, or just delete the file.
If you have a complicated authorization requirement you can manually create a token file by pasting a Github token with only the gist permission into a file called ~/.gist. You can create one from https://github.com/settings/tokens
This file should contain only the token (~40 hex characters), and to make it easier to edit, can optionally have a final newline (\n or \r\n).
For example, one way to create this file would be to run:
echo MY_SECRET_TOKEN > ~/.gist
If you´d like gist to use your locally installed GitHub Enterprise https://enterprise.github.com/, you need to export the GITHUB_URL environment variable (usually done in your ~/.bashrc).
export GITHUB_URL=http://github.internal.example.com/
Once you´ve done this and restarted your terminal (or run source ~/.bashrc), gist will automatically use github enterprise instead of the public github.com
Your token for GitHub Enterprise will be stored in .gist.<protocol>.<server.name>[.<port>] (e.g. ~/.gist.http.github.internal.example.com for the GITHUB_URL example above) instead of ~/.gist.
If you have multiple servers or use Enterprise and public GitHub often, you can work around this by creating scripts that set the env var and then run gist. Keep in mind that to use the public GitHub you must unset the env var. Just setting it to the public URL will not work. Use unset GITHUB_URL
If you cannot use passwords, as most Enterprise installations do, you can generate the token via the web interface and then simply save the string in the correct file. Avoid line breaks or you might see: $ gist -l Error: Bad credentials
If you need more advanced features you can also pass:
NOTE: The access_token must have the "gist" scope.
If clipboard or browser integration don´t work on your platform, please file a bug or (more ideally) a pull request.
If you need to use an HTTP proxy to access the internet, export the HTTP_PROXY or http_proxy environment variable and gist will use it.
Thanks to @defunkt and @indirect for writing and maintaining versions 1 through 3. Thanks to @rking and @ConradIrwin for maintaining version 4.
Licensed under the MIT license. Bug-reports, and pull requests are welcome.
May 2018 |