I would like to ask for your advice on managing Git's repository.
Is there a good way to manage a single system program with 100 features in one system?
I am currently expecting the following two items.
(1) Manage all 100 functions in one repository
(2) Manage one feature at a time in a separate repository
(3) Others (I can't imagine it at all)
Until now, Subversion has managed functions 1 to 100 in a single repository.
There are about 20 developers, all of whom have access to all features 1 to 100.
We checked out only the features we needed at any time, and at that time we removed the features we didn't need from the local area.
With Git, the functions I need now are from 1 to 10, but I'm afraid that even unnecessary 11 to 100 are local, and I thought it would take a long time to pull.
However, I am not sure if I can manage as many as 100 repositories if I use a different repository.
It's not so realistic to create 100 directories each and clone each.
If you need 10 more features, I think it's a lot of work to pull 10 times.
In this case, how do you create and manage a repository?
Please lend us your wisdom.
I don't know how big the system is, but I wonder if it's huge enough to exceed a few GB of code as a whole.
If not, Git gets the updates in increments, so I don't think it's a problem to get all the features every time.
Git has a function called submodule, which allows you to browse to another repository from the repository.
This feature also allows you to update all child repositories at once to the latest version, or to specify the child repository to be referenced by each parent repository as their branch or commit.
Using this feature to create a repository for each of the 100 features, and it should be on the one system side that brings them all together.
Summary of understanding points you want to keep in mind for Git submodule - Qiita
© 2024 OneMinuteCode. All rights reserved.