Git usage specification


1. Basic operation of GIT

-Git init if a project needs to be managed using git, it needs to be initialized
	-Git status: check the status of the current code (red: in the Development Zone, green: in the temporary storage zone, nothing to commit: there is no change in the Development Zone)
	-Git checkout - B develop create and switch to the development benchmark branch develop
	-Git checkout - B feature / XXXX creates a function branch based on development. It is recommended to develop the function branch with feature /
	-Git add. Put the code in the staging area
	-Git commit - M function name puts the code from the staging area into the local warehouse
	-Git checkout branch name switch to a branch
	-Git merge feature / XXXX is a branch merging into another branch
	-Git push pushes the code from the local warehouse to the remote warehouse
	-Git pull pulls down the latest content of the remote host and merges it directly
	-Git fetch pulls the latest content of the remote warehouse locally. After checking, the user decides whether to merge it into the working local branch
	-Git log view log
	-Git log -- oneline view the concise log (recommended)
	-Git reset -- hard XXX is restored to a node. The node is a commit submitted, which needs to be viewed using git log

2. Precautions

-It is not allowed to write any code or modify any bugs in master and development. It is prohibited in development!!!!!!
	-Developep needs to be created based on mater. If there is a problem with the developep code, it also needs to be rebuilt based on mater
	-All functional branches must be created based on development, which should include all functional branches
	-Merging between branches is prohibited, including test branches, pre release online branches, etc
	-If there is a bug in the development code, it is forbidden to modify it directly in the development branch. You need to create a bugfix branch to modify it
	-The release branch is a pre release branch

		① It includes all new features and necessary fixes
		② It has been thoroughly tested. If the above two points are met, it is time to start generating a new release

	-If there is a bug in the master and release code, it is forbidden to modify it directly in the master and release branches. You need to create a hotfix branch to modify it
	-Strictly speaking, the master and development codes are basically consistent, and it is best to be completely consistent

	-Development is the development benchmark branch, and all [function branches] must be created based on development