My team has a GitHub organization account. A lot of the work I do results in one-off scripts that we want to be able to have on our organization page but that aren't big enough projects to justify their own repository.
Is there any way to associate Gists with GitHub organization accounts?
If not, what's the best way to 'check-in' or associate smaller scripts into GitHub's shared organizational repository?
Found the answer on Github's support site (now archived here):
The answer, as of October 2010, is No.
It's planned but we don't have a timeframe available -- sorry about that.
So here's a crazy hack. If you create a new github account and make a bunch of gists, you can then convert that account into an Organization and the gists stay associated with the new Organization.
Big caveat: you won't be able to create any new gists for that Organization. But you can edit existing ones. :-\
For the time being, I think it would be best to start a new organization repository and put all your gists in there. Use the repository interface on Github to manage your gists.
If you want the gists to be publicly available, create a public repository. If you want them to be internal, create a private repository and limit the audience to your organization's users. As bonus perks, you can also add media and reference them from the gists. I think one could also argue that it's easier to navigate a Git repo than a user's list of gists.
So, seems a gist behaves a lot like, well... a Git file!
