-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose gists "public" attribute to allow secret gists #2
Comments
I'd certainly take a patch. I guess the most simplistic would be making it use public: ${PUBLIC_gists:-true}. Or you can suggest something more sophisticated. |
Took a while :) https://gist.github.com/Unode/7e65f53bb152485d038b Uploaded using the patch itself. |
I clearly haven't quite understood this commenting system...
Yeah, I'm finally caught up on reading mails again. ;) If I should fall behind again, IRC on freenode will probably remain the quickest way to gain my attention. Please use [[ ... || .. ]] rather than [[ ... ]] || [[ ... ]] on line 38. Looks good otherwise. |
Updated. Same address. |
Alright, it's in version 2.27 |
Cool, cheers |
Hi Bo,
I'd like to be able to default to secret gists when using the github service.
I see in the API docs that "public:false" is the default and I also see in wgetpaste that "public: true" is hardcoded in the gist JSON request. Is there any way this could be exposed so I could customize it from a config file?
Thanks
The text was updated successfully, but these errors were encountered: