How do I handle plugin replicas using git?

I have a little dvcs design question: I have a project that I post on github. I also have several plugins that I wrote for the project, but I do not want to include in the main code, because they are additional plugins.

In svn, I just created an additional directory containing all the plugins. Users can specify their svn: externals to each plugin in the directory. With git, I'm not sure if I should create repos on plugins and have a separate branch for each plugin that users can modulate, or if I have to have a completely separate repo for each plugin that can be modulated. Any thoughts?

+3
source share
2 answers

I would create a separate repo for each plugin that can be modulated. Git repositories work best when they contain only one project, and the branches in this repo relate to each other (instead of storing each project in separate, unconnected branches in the same repo).

+4
source

You can reference the global repo plugin, that is, the repo that will contain all the submodules (one for each plugin)

In your main repo, you can only refer to the fact that the repository is a “global plug-in”, which is a “stable configuration” of plug-ins (“stable” because “exact versions of plug-ins work well together”)

0
source

Source: https://habr.com/ru/post/1734455/


All Articles