Support for multi-file gists #19
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I've patched |
|
Awesome, thanks! |
* 'master' of https://github.com/indirect/gist: oh right version help now mentions multiple files and - for stdin refactor, because... why so complicated Don't need index for each block Add support for multi-file gists gotta build it build it build it Use the code that's already there Using '-' as file name forces gist to read from stdin. Add curl's cacert.pem so we can validate Github's SSL certificate HTTPS support for the newer, safer Github Conflicts: lib/gist.rb
ConradIrwin
pushed a commit
to ConradIrwin/gist
that referenced
this pull request
May 3, 2013
gracefull error on windows.
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch adds support for multi-file gists. Example
$ gist file1.txt file2.txt
Or, in a situation where I want to show someone my merge conflicts:
$ git ls-files --unmerged | cut -f 2 | uniq | xargs gist
See also #4.