Common git commands and scenarios (I)-Online code update and project code submission

Git was used in recent work and a simple record was made:

1. project view or execution for test environment and online environment: git initialization: git initgit pull code: git pull git@127.0.0.1: Project. git 2. project development, used in the development environment: (After development on the basis of 1) First, a configuration is involved in code submission. The configuration content is to mark the user who submitted the code modification, you need to set the parameters "name" and "email" by running the following command: git config -- global user. name "lixinglei" Git
Config -- global user. Email "lixinglei@xxxx.com"
After the configuration, you can view it through git config -- list:

[Lixinglei @ bogon ~] $ Git config -- listuser. Name = lixingleiuser. Email = lixinglei@xxxx.com

The configuration change belongs to the user-level (global) configuration. After the configuration is complete, all git repository submissions use this name and email

View the current changes. It is usually used before commit to confirm that git status is more advanced than git status. view the specific changes: git diff (if a new file is added: git add file1.py if any file is deleted: git RM file2.py) after the code is confirmed to be correct, the code is submitted. The commit is committed to the local machine: git commit file3.py service/file4.py-M "version note" before pushing the local code to the server, you usually need to update the online code. This pull operation will automatically merge the local merge code: git pull git@127.0.0.1: Project. git
Finally, the local library code is pushed to the server: git push git@127.0.0.1: Project. Git