What Git strategy to use when working with multiple people?

Question

git

Colleagues, what is the best strategy for working with Git on a production server?
Now we have
On the server:
1) --bare repository
2) site working folder
Locally
3) clone from --bare repository.
The exchange goes with --bare, it throws it through the post-update hook into the combat folder.
Only build build files are exchanged everywhere and there are no problems, but now when several people work on a project on the server, you need to have a full development copy of the repository with package.json and other files that are not in the site’s combat folder.
How to deploy to the combat folder of the site in such a situation?
in hooks --bare of the repository to make a filter and send only assembly files to the working one? or assembly directly on the server to carry out? or for deployment and developers to do separate repositories related to it?

Answer 1

Use CI/CD. Build in it.
Deploy tags explicitly.