We are currently using SVN to develop an internal application that has most of its functionality in plugins. In our approach to switching git, this application causes some headaches regarding what is best for handling such a project in git.
those. should we put each plugin in our own git repository? This may seem like a logical choice, because plugins are mostly independent of each other and quite autonomous (they simply use the main application for the functionality of the framework and manage common functions), which are often developed by different people and sometimes become outdated. However, now there are more than a dozen plugins with even more, and to create an entire project you usually need to check all (or most) of the plugins one at a time. And there seems to be no easy way to check ALL of them right away, i.e. There probably should be some kind of “list” so that people know what to get and what not.
Putting just one git repository, on the other hand, seems out of sorts with git, especially. since we will wear the old dead code and work on one plugin, it will be necessary to check a lot of code (although then most developers working on it would still check everything). Also, branching will always expand everything (which makes, for example, cross-testing branching functions difficult if plugins cannot branch out individually)
One idea is to use submodules, but I don’t know if the overhead (mental overhead, I mean) is more than a gain (or we get less than we lose using the “one by one” approach )
How will you handle this project in git?
source
share