3 ms·
The one-repo-for-old-projects solution works in some cases, but not really for mine. As a contract developer I often have projects that are under active develop
by sant0sk1 15y ago
The one-repo-for-old-projects solution works in some cases, but not really for mine. As a contract developer I often have projects that are under active development for a few months and then go into "maintenance mode". In this case I want separate repos for when maintenance needs to happen. Otherwise that one repo is a mess.
I believe this is the kind of problem that CodePlane solves. And I agree with you that its great to see projects like this present competition and make GitHub better in the long run.
- arturadib 15y agoIt's a hack of course, but if the changes are really that occasional, the pain is negligible: all you need to do is to commit twice for every project change (once for a sub-directory containing the project repo, once for the root repo). If a project becomes active again, simply take it out of the master repo and push it as a new repo. It's really not that bad. But then again, things change if you have collaborators...
- lucian1900 15y agoCan't you just use branches for this? Sugar code (git.sugarlabs.org) generally gets a new branch for each major release, which can be maintained separately from master.