How to organize the work with a git repository in the team?

There is a conditional command in three, two new and one older. How best to arrange access to the repository?

  1. Beginners work under one account, make a branch, shove, senior developer merge you work into trunk branch to develop, etc.
  2. Beginners make the forks of the repository team, doing branches, shove, make a pull request to the repository team and there's already a senior developer it accepts/rejects

What other ways are there and what the correct method from the list?
2 answers
June 10th 19 at 15:43
Beginners work every under your account.
2 main branches - dev and master.
Rookie branching from dev, does the job and pushes to the server.
Senior makes code review and merit in dev.
Test the code in branch dev.
If the tests passed - Merz in master.

Of course beginners we cut access to the merger and do not allow direct push to master.

You can still run the Linter and tests before committing, so as not to accidentally pour something outside.
OK, thanks for the reply. Overall, the pool requests only solution for open source and not for private projects, right? - Herbert commented on June 10th 19 at 15:46
no , not true. How you found the connection between the pull requeste and open source? It's like a warm soft.
You can even a folder to archive and send by mail, if only it was convenient you.
Just the solution with a fork for a crew of 3 people is too much )) - Kameron_Hilpert34 commented on June 10th 19 at 15:49
IMHO, it is better to branch from the master.
Possible conflicts safer to disassemble when merzh in dev. And the probability of delay for a fight that should not be there - below.
Especially when the team is not very experienced and developed. - alda_Nicolas46 commented on June 10th 19 at 15:52
June 10th 19 at 15:45
1. Pay accounts? why do beginners can't work every under your account ?
2. IMHO ppl were excessive, a separate thread is quite enough.

Actually something like git flow can be implemented in any team, regardless of the experience of participants.

Find more questions by tags Organization of the workBitbucketGitWeb DevelopmentVersion control systems