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

Question

git

There is a conditional team of three people, two beginners and one older. What is the best way to organize access to the repository?

1. Beginners work under one account, make branches, push, a senior developer merged branches in develop, etc.
   
2. Beginners fork the team repository, make branches there, push, make a pull request to the team repository and there the senior developer accepts / rejects it
   

What other ways are there and what is the correct way from the list?

Answer 1

Beginners work each under their own account.
2 main branches - dev and master .
The newbie branches from dev , does the work, and pushes to the server.
Senior reviews code and merges to dev .
Test the code in the dev branch .
If the tests pass, merge into master .
Naturally, for beginners, we cut access to the merge and prohibit direct pushing to master .
You can also set up the launch of the linter and autotests before the commit, so as not to accidentally upload something that is not working.

Answer 2

1. Accounts paid? Why can't beginners work each under their own account?
2. IMHO forks are redundant, a separate branch is enough.
In fact, something like git flow can be implemented in any team, regardless of the experience of the participants.