Should I use pull-request in git in a team of 2 people?

Question

git

Good day.
Please describe the scheme of working with git in a team of 2 people, one of which is the owner of the project, the other is a contract programmer on a permanent basis. Many small tasks for 2-3 hours each, that is, 3-4 tasks per day.
There are no conflicts, the amount of work of the 1st programmer is also small or may not exist
at all. Repository for bitbucket.
I would be grateful for a detailed answer.

Answer 1

worked in this vein in a team. The owner of the account on bb creates a repository with a working project and creates a develop branch from the master branch gives an invitation to this repository to team members, they download it to themselves. Personally, I worked through the soursetree application. Then everyone deploys the project locally (we worked with the gulp assembly) And creates its own branch from the developer in which it solves its own separate task.
Upon completion of the work, he sends his branch to the repository (creating a branch of the same name there, this is basically done by soursetree) Requests a pull request, someone from the team checks his work and either sends it for editing, or, if everything is fine, merges it into the developer, which is on bb . We also used Trello to show who is working on what and at what stage each process is. If you need to clarify something, I'll be happy to help.

Answer 2

In a nutshell:
from the master of the maidens a branch. Developers only have access to devs. There is a separate branch for each task. When ready, the branches of tasks are merged with the maiden branch, if everything is ok, then the maidens will be merged with the master. Master always keep slick

Answer 3

google git flow