Reputation: 169
I'm a little bit confused about the workflows i've found. Is it right to have a bare repo, a stage repo , a live repo and a stage repo ? Isn't it really large for big projects ? I mean, so the space is four times bigger ...
Or what else can i do ? one bare repo, which copies the files ?
Upvotes: 3
Views: 693
Reputation: 129744
You would want a combination of branches and tags to follow your work. Here is what we do:
http://dymitruk.com/blog/2012/02/05/branch-per-feature/
Upvotes: 0
Reputation: 1510
If you need to keep different "versions" of the codebase for developing new features vs. QA'ing "finished" features vs. the stable build out in production, branching in GIT is a good way to. You can have a branch per version, and that ought to allow you to work on whichever version as needed.
Upvotes: 0
Reputation: 1526
You probably want to use branches. http://progit.org/book/ch3-1.html
Upvotes: 3