Usually, when I launch a new application, I would create a new git repository for it. This is well received and plays great with Github when I want to share my code.
At work, I work in a service-oriented architecture. One very common example is to add code to two different applications at the same time - perhaps by adding a RESTful model to one and a web interface to manage it differently. When using separate git repositories in this case there are warts.
Here's what I see as the disadvantages of creating separate repositories:
- I need to commit twice
- I cannot correctly correlate the corresponding commits.
- There is no place to return and track history - I would like that I could bring up all my obligations for the day in one place.
- Forgetting one repo or another is getting
On the other hand, I used perforce a lot, and in his one giant repository model there are also many warts. Perforce has features to help you with this, git not.
Does anyone else encounter this situation? How did you deal with this? What worked well and what didn’t?
source
share