Git Workflow
Pull Request
The master
branch is protected and commits can only be added via a reviewed PR.
Commit Message
Note
See Conventional Commits for more details
Use all-lower-cased messages with a prefix. The prefix can be one of the following.
fix
: bug fixfeat
: new featuredoc
: add/edit documentsci
: construct CI pipelinestyle
: adjust code stylerefactor
: code refactorperf
: tune performancetest
: testchore
: other stuff
The title should be a manageable length. Details can be added in the body. For example, a commit message like this is probably a bad idea.
feat: added new features for user authentication and authorization, including login, registration, password reset, and role-based access control
And it can be improved as
feat: implement user authentication and authorization
- add login, registration, and password reset
- enforce role-based access control
Checkout a remote branch
Note
See git fetch
a remote branch - Stack Overflow for more details
Suppose your teammate pushed a branch named fix-grid-env
and you want to continue to work based on this branch, you can use git switch
to checkout this branch.
git switch fix-grid-env
Solving bad situations
Dangit, Git!?! is a great resource for solving bad situations in Git.