Answer the question
In order to leave comments, you need to log in
How to organize work in a team through git?
Good morning, now I work alone and the process looks like this:
- On the local PC I write code, test and do git commit and git push
- On the server I do git pull
Now a couple more developers have appeared in the team. My plan is as follows:
- Each of them, receiving a task, creates a branch from master for this task
- Commits to this branch
- I check this branch and merge into the master
That is, they should not have pushes to the master and, it seems to me, not there must be access to the server so that there is one person responsible for the deployment.
Am I right about teamwork?
Answer the question
In order to leave comments, you need to log in
As already advised by git-flow (eg by Vincent Drazen). Developers have the right to merge their branches in dev, so requests are not needed (they are good for requests from remote developers), from dev you collect and run tests daily (CI), then from dev you collect the release and throw it into master, this already makes a separate Human. On the server (if we are talking about prod) git should not be, there should be a normal CD. And yes, developers have no access to combat. The rest was correctly described.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question