I'm introducing Git in our company. I have several applications that all interact together via sockets, and now, it is about to decide whether I should use
- separate branches for different parts of my application, or
- separate Git projects.
I also want to use tags for revisions; if I use branches, I have to tag like
branchnameV1.0, but if I use separate Git projects I could tag likev1.0`.
What would be the most conventional method for doing this?
Best How To :
Separate Git projects: branches are interesting if you intend to merge common code source.
But if your apps are independent (in development, even though they are somehow linked in runtime), a git repo per application will work better.
It will allow for each app to follow its own development lifecycle, with its own set of tags and branches.
If you want to keep track which versions of those three apps are, at a given time, working together, you can create a fourth repo, and register the first three as submodules.