A. When I ran into some issues and got a error.log
, the best way to report bugs is gist-it error.log
and post the link to it on the issue you created.
B. Somebody asked me to provide a repo to reproduce a bug, so I made it locally and upload it to gist in order to share with him without creating a repo for that.
yarn global add gist-it
# OR
npm i -g gist-it
gist-it ./npm.log
gist-it lib/foo.js bin/bar.js
# or even glob
gist-it "*.js" "css/*.css"
gist-it --help
By default the gist will be published anonymously, to publish it under your account, you need to generate an access token at https://github.com/settings/tokens/new, remember to select gist
scope:
Then store it in gist-it
:
gist-it --set-token $the_token_you_just_generated
Or use a token without storing it:
gist-it --token $your_token
To not to use stored token for once:
gist-it --no-token
To update an exisitng gist, append the command with --id existing-gist-id
.
git checkout -b my-new-feature
git commit -am 'Add some feature'
git push origin my-new-feature
gist-it © egoist, Released under the MIT License. Authored and maintained by egoist with help from contributors (list).
egoistian.com · GitHub @egoist · Twitter @_egoistlily