How teams actually use git

You already know enough commands. What comes next is the part no man page teaches: how several people work in one repository without getting in each other's way. There are more rules here than commands, and they rest on agreements rather than on anything git enforces.

There is one main pattern. Every task lives in its own branch until it is ready, and it reaches the shared branch through a separate step where somebody reads it. This is called the feature branch workflow, and almost every team works that way.

One task, one branch

The cycle of a single task looks like this. Treat it as a checklist: go top to bottom and you will not forget anything.

1. Switch to the main branch: git switch main.
2. Pull what is new on the server: git pull