D
D
Dos2019-12-25 01:15:12
git
Dos, 2019-12-25 01:15:12

What is the best way to organize team work? One repository or several?

Hey! We started working in a team of two people. front and back end. Immediately the question arose of how best to maintain a repository on github / gitlab? The partner suggests dividing the repositories logically into Front and Backend, and each one works in its own. I'm leaning towards a mono repository, where projects are divided into api, frontend, storage and so on folders. Since the project is "sausage" at the initial stage (constant changes), it will be easier to make such changes in one repository. They changed the field and, without waiting for the front guard, I climb myself and correct this field without waiting for him. And already when everything settles down more or less, we spread it to different repositories, services, microservices, and so on.
His main concern is that the commits will be lost. But I suspect that different repositories will give more problems than losing commits. In addition, you can always start a project on a new turnip and maintain both versions in parallel, for example, as they do in Yii, Yii2, Yii3. What do you think? How do you organize work in a team of 2 or more people? It would be nice to paint the pros and cons of both options.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
S
Saboteur, 2019-12-25
@pro-dev

Do it in different.
Do you have frontend and backend in the same file? In the same folder?
If not, then what difference does it make to go to the next folder or go to another repository in the next folder?
But the commit logs will not be confused. And when everything settles down, it will also be easier - you don’t need to spread anything.
For 2 people it doesn't matter at all. It's easier for two to get along. But in the future, if everything is supposed to blow up, why not do it now?
Or you take another front-ender in a month and start telling him where the front is, where the back is and what it is going to be, give access to everything, and tell him where not to go. And if the front and back are different at once, then you don’t need to do anything.
In addition, right now the commit log will not be polluted with unnecessary things that are important only to one of you.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question