Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

use file basename by default #93

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
4 participants

goodell commented Apr 19, 2012

The github API doesn't seem to like file names with a '/' in it, like
you would get if you executed gist /tmp/foo.txt or
gist subdir/bar.c. This yields a "422 Unprocessable Entity" error
which can be very confusing. Using the file's basename eliminates this
problem. This behavior can be disabled by passing --no-basename to
gist.

@goodell goodell use file basename by default
The github API doesn't seem to like file names with a '/' in it, like
you would get if you executed `gist /tmp/foo.txt` or
`gist subdir/bar.c`.  This yields a "422 Unprocessable Entity" error
which can be very confusing.  Using the file's basename eliminates this
problem.  This behavior can be disabled by passing `--no-basename` to
gist.
963a5f6

goodell commented May 5, 2012

updated to 963a5f6 to avoid accidentally conflating a separate fix with the basename issue

tosik commented Jun 17, 2012

+1

mfilej commented Feb 16, 2013

Just ran into this and the error is indeed very cryptic.

A question regarding this patch – I'm probably missing something here – but what is the purpose of the --no-basename option? Wouldn't using it just result in an error?

Contributor

sickill commented Apr 29, 2013

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment