Background

GitHub’s Gist is a nice and fun way to quickly share code snippets.

 

Limitations

Though, fun it has certain stubborn limitations.

 

Outline

1. Cannot change a snippet viewership from public to private
2. Cannot name a gist

Security

Viewership

Yes, one can promote a gist viewership from private to public.

But, it is one traffic.

One can not revert back to private.

 

Customizable

Naming

Gists are automatically assigned the name of the first file created.

If other files are added to the same gist, the gist will take the name of the first file ordered alphabetically.

 

 

Referenced Work

1. Stack Overflow
   • How to change the name of a gist in github?
     Link
2. Gist
   • Gists: Bring back the (editable) title (and descriptions) #194
     Published:- 2014-May-16th
     Link
3. Github
   • Feedback
     • Change gist name and description #13772
       Link

 

I’m going to talk about it today

Michael Huse ( mhuse )

Back in 2014-May-20th, here is an animated GIF that Michale Huse ( mhuse ) used to illustrate his ask.

https://github.com/isaacs/github/issues/194 ( Link )

Examples in the wild:

Optimally, I’d prefer something like this (editable repo description):

… Or this (editable issue titles):

 

Summary

For a very good open-source, collaborative tool to maintain such a sturdy ask list is informative as to where we really are in terms of openness and collaboration.

These are well-intentioned people who have done the following:-

1. Found an area that can be bettered
2. Narrowly defined that area
3. Written up the issue
4. Tactfully, offered remediation path

Yet, the issue stays dormant for years.

Affecting each and everyone, with no feedback as to why the issue is not even being reviewed.