How to properly organize a Git repository?

Question

git

A project of medium complexity, how many branches to create for convenient work?
We will be 8 people, maybe a little less
Interested in the correct organization of the Git repository

Answer 1

git was originally designed so that branches weigh almost nothing.
Use branches however you like.
Ideally, make one master branch, where already checked "beautiful" commits are uploaded for the report, and develop, into which commits are uploaded to check already general changes. And locally, each developer can make a branch for each new task, which is then merged into develop

Answer 2

I use Git all the time. I usually create a master branch, in which I post all the current changes in the program and a developer branch. in which I try to refine some functionality or do something new in the program. There is also a bugfix branch where a bug is fixed and then fixed. This structure is good because:
1) you have an up-to-date state of your program;
2) everyone can view the changes in the developer and thus perform a little control for the development;
3) the bugfix branch is a very necessary thing. There you can find the status of bugs.