Server Fault is a question and answer site for system and network administrators. 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

Being a consulting company, we work on dozens of projects, some small and some large. We use the 10-repo business account in GitHub and it is getting crowded.

Most of our projects are not active. We deliver it to the client but maybe we will hear back from them in 6 months or a year asking for a bug to be fixed or another feature to be included.

I would like to move these projects into a single repository, while retaining their history. I would like to establish a Repository such as "Completed Projects" where the code and history just goes to die unless I need to make changes in the future.

If I need to work on them, I can do so in this repository, or if there is going to be a lot of work, I can pull it out into one of my unused repositories and work on it there.

I'm trying to avoid paying large monthly fees for repositories of inactive code.

How can I do this with GitHub?

I do realize I can host Git myself on my server as an alternative.

share|improve this question

closed as off topic by Sven, voretaq7 Dec 7 '12 at 3:54

Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here.If this question can be reworded to fit the rules in the help center, please edit the question.

You should just be able to fetch the branches of interest from the existing repositories into your "completed projects" repo, and git will work out that there are no common commits and deal with it appropriately. Push that up to github, and you're done.

share|improve this answer
This option will retain the history? – Jason Jul 29 '11 at 2:14
Of course, just like any other fetch into another repository. – womble Jul 29 '11 at 12:23

Why not just clone the repository and archive it, saving github for active projects?

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.