appwiki:git

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
appwiki:git [2024/04/01 05:50] – [Command Git cmds] yingappwiki:git [2024/04/11 08:51] – [Command Git cmds] ying
Line 7: Line 7:
 ====== Command Git cmds ====== ====== Command Git cmds ======
  
-  * start the git-cmd.exe and now you are in a cmd with git built-in+The Three States of Git 
 +  * **Modified**: A file is modified when you have changed it but have not yet committed it to your repository. It is only changed in your working directory. 
 +  * **Staged**: A modified file becomes staged when you **add it** to your staging area. Here, Git has it marked as ready to be committed in the next snapshot. This means you've told Git to include the updates from this file in the upcoming commit. 
 +  * **Committed**: Once a file is committed, it means that the data is safely stored in your repository's local database. This updates the commit history with a new snapshot of your project at the time you made the commit. 
 + 
 +Cmds 
 +  * start the git-cmd.exe and now you are in a cmd with git built-in, or add git path to your cmd session: <code>set PATH=D:\path_to_git_folder\bin;%PATH%</code>
   * create a default user if you have not <code dos>   * create a default user if you have not <code dos>
 git config --global user.name "AnyOne" git config --global user.name "AnyOne"
 git config --global user.email "anyone@any.what" git config --global user.email "anyone@any.what"
 </code> </code>
 +  * list config <code dos>git config --list</code>
   * create a project folder <code dos>mkdir SuperWebProj   * create a project folder <code dos>mkdir SuperWebProj
 cd SuperWebProj cd SuperWebProj
 touch index.html touch index.html
 +</code>
 +  * create ignore list inside git directory, create .gitignore file <code dos>
 +# ignore folder, ignore type of files
 +__pycache__/
 +*.py[cod]
 +
 +# ignore build folder
 +build/
 </code> </code>
   * cd to the folder where you want to create a repo <code dos>git init</code>   * cd to the folder where you want to create a repo <code dos>git init</code>
Line 24: Line 39:
   * check status <code dos>git status</code>   * check status <code dos>git status</code>
     * optional: you can change branch name like <code dos>git branch -m master main</code>     * optional: you can change branch name like <code dos>git branch -m master main</code>
-  * add everything in the directory that is changed <code dos>git add .</code>+  * add everything in the directory that is changed  
 +    * all new and modified files: <code dos>git add .</code> 
 +    * all new and modified + deleted files <code dos>git add -A</code> 
 +    * all modified + deleted files <code dos>git add -u</code>
   * to view change log <code dos>git log</code>   * to view change log <code dos>git log</code>
   * use git to zip folder <code dos>   * use git to zip folder <code dos>
 git archive --format=zip -o project_code.zip HEAD project_code git archive --format=zip -o project_code.zip HEAD project_code
 </code> </code>
 +  * git download a project: cd to root of your project folders, (note: clone will create root folder of the git project, best no space, AnBn style naming) <code dos> 
 +git clone https://proj_url/project.git 
 +</code> 
 +  * git remote source for fetch and push, (this only deal with remote repo), check remote source <code dos> 
 +git remote -v 
 +</code> 
 +  * git list branch,  
 +    * both local and remote branch<code dos>git branch -a</code> 
 +    * both local branch<code dos>git branch</code> 
 +  * git check all changes to files in detail, this is before changes added (not yet commit) <code dos>git diff</code> 
 +  * always get source update before push <code dos>git pull origin branch-name 
 +git push origin branch-name 
 +</code> 
 +  * create branch for a feature or a issue <code dos>git branch export-feature</code> 
 +  * switch branch <code dos>git checkout export-feature</code> 
 +  * push to remote repo <code dos>git push -u origin export-feature</code>
 Extra Tips: Extra Tips:
   * you can use vscode to open the folder project (the one with .git hidden folder), vscode will auto know it is a git project and it has some built-in tool to help you instead of using the git cmd   * you can use vscode to open the folder project (the one with .git hidden folder), vscode will auto know it is a git project and it has some built-in tool to help you instead of using the git cmd
  • appwiki/git.txt
  • Last modified: 2024/05/08 06:01
  • by ying