How to organize repositories for different developers?

Question

git

Hello everyone, I am working on a project implemented in Yii2.
There are programmers, and there are layout designers, the task is to separate accesses, i.e. the layout designer should have access only to the frontend folder, and the programmers can climb everywhere, but at the same time it’s all one git repository ( joxi.ru/MAjGnZ8fvB39or ), there was an idea to make a repository in repositories, but git sees that the internal folder belongs to the repository. How to be? =)
If it's a little simpler: there is one project in which the layout designer cannot be given the backend code, otherwise he will like it and copy it for himself.
I see it as different turnips for the back and front folders ... but maybe there is a better solution.

Answer 1

git submodule ?

Answer 2

To put it a little simpler: there is one project in which the layout designer cannot be given the backend code, otherwise he will like it and copy it for himself.

If you don't want to give the code, then you don't want to give the repository. To work, the layout designer will need a local copy of the turnip. Since he will have such a copy, if he wants to, he will pull out the files. Git takes a snapshot of the entire tree, so it's basically impossible to reliably restrict access to the contents of files in other folders.
Make two different turnips for front and back, you will get used to it and you will like it.
This is the most reasonable solution. Even if there was no question of access control, it would also be convenient in terms of deployment. Since you are talking about the front and back separately, it means that it is convenient for you to develop them separately, and since it is convenient to develop them separately, it will probably be convenient to release them separately. And this is a direct signal for division into different turnips.
PS I looked at your screenshot, there are strangely many folders outside the frontend and backend, what do you keep in them?)

Answer 3

I would set up hooks with a breakdown of rights by group. I did this in my projects, everything works fine.

Answer 4

https://habrahabr.ru/post/75990/adw0rd.com/2015/6/26/git-directory-permissions
_