Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Say you have a couple of projects that you want to host on GitHub, and they're all pretty small (i.e. each one is a single bash script with less than 100 lines).

Even though they're relatively small, they can still be complex in that size, and a gist seems inappropriate. On the other hand, making an entire repository for a single file seems a bit much, is it? At what point should a gist become a repository, if ever?

You could also just collect all the scripts in one repository, but that'd be messing a lot of stuff that has no relation between them.

I've searched and thought about this problem, but have not found a satisfactory answer.

share|improve this question

closed as not constructive by Karan, Dennis, CharlieRB, BBlake, Tog Feb 5 '13 at 14:24

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

I think this is a valid question. For example, I have two related files, an implementation and a file for testing the implementation. The concepts in the implementation are more suited for a gist (IMHO), but there is the test file as well that is related. Does this imply that it should be repository instead of a gist? – Josh Petitt Aug 23 '13 at 18:06
This question was closed because it may not have an objective answer. Nevertheless, I do think that it's constructive. Some googling leads to this discussion on the topic:… – Javier Parra May 19 '15 at 1:45
up vote 2 down vote accepted

If the set of scripts evolves together/are used together/have some kind of relationship (apart from "I wrote the bunch"), create a single repository for them. If not, slice and dice as appropiate. git is quite lightweight.

share|improve this answer
But should I separate them as whole repositories for a single file? I know that in practice it won't be that much of a diference storage-wise, but isn't it one of those “kill a fly with a bazooka” situations? Would a gist be more appropriate? Why or why not? – user137369 Feb 5 '13 at 3:02
It is your call, at the end. If they are yours only, one repository is fine. – vonbrand Feb 5 '13 at 3:08

Not the answer you're looking for? Browse other questions tagged .