markdown 日常工作流程中常见的git命令

Posted 2021-05-06

# Git Cheat Sheet

## Initial Setup


### [Initialize a repo](https://www.kernel.org/pub/software/scm/git/docs/git-init.html)

Create an empty git repo or reinitialize an existing one
```shell
$ git init
```

### [Fork a repo](https://help.github.com/articles/fork-a-repo#step-1-fork-the-spoon-knife-repository)

Click the "Fork" button at the top-right of any repository's GitHub page.


### [Clone a repo](https://www.kernel.org/pub/software/scm/git/docs/git-clone.html)

Clone the codepainter repo into a new directory called codepainter:
```shell
$ git clone https://github.com/jedhunsaker/codepainter.git codepainter
```


### [Setup Remotes](https://help.github.com/articles/fork-a-repo#step-3-configure-remotes)

First, let's see a list of the repositories (remotes) whose branches you track:
```shell
$ git remote -v
```

Oh, it looks like we haven't setup upstream. Now is the time:
```shell
$ git remote add upstream https://github.com/username/codepainter.git
$ git fetch upstream
```


## Every-day Workflow


### [Branching](https://www.kernel.org/pub/software/scm/git/docs/git-checkout.html)

When working on a fork, you could be switching between different branches quite commonly. As such, you generally want to stay off the master branch and work on your own feature branches so that master is always clean and you can base new branches off of it.
```shell
$ git checkout -b <new_branch_name>
```

If upstream has a special develop branch or something, you can checkout that branch separately, but setup tracking so you can sync it up from time to time. Like the master branch, don't work directly on this one. Try to keep it clean.
```shell
$ git checkout -b <new_branch_name> --track upstream/<remote_branch_to_track>
```

Maybe you made some progress on a branch at work, but now you want to continue work at home. In that case, you're dealing with your own fork's branch, so you'll checkout from origin.
```shell
$ git checkout -b <new_branch_name> --track origin/<remote_branch_to_track>
```

Use the `-B` option flag to force it.


### [Switching Branches](https://www.kernel.org/pub/software/scm/git/docs/git-checkout.html)

First, you'll want to know what branches are available in your working directory:
```shell
$ git branch
  develop
  feature_x
  master
```

Now, you can easily switch between branches with git checkout:
```shell
$ git checkout master
$ git checkout develop
$ git checkout feature_x
$ git config --global alias.co 'checkout'
$ git co master
```


### [Status](https://www.kernel.org/pub/software/scm/git/docs/git-status.html)

Not sure if you're working on a clean branch? Want to see what files have changed? Git status will show you a report.
```shell
$ git status
```

### [Staging Changes](https://www.kernel.org/pub/software/scm/git/docs/git-add.html)

Now that you've added or modified some files, you need to stage those commits into "the staging area." Think of git commits like an array of airlock hatches on a space ship. On this space ship, you can only open the door to one airlock at a time. When you open the hatch, you can put stuff in or take stuff out at will. Not until you've closed the door have you committed those changes (git commit) and not until you hit the red button do all those hatches open up into space (git push).

You can stage inidividual files or all files at once.
```shell
$ git add foo.js
$ git add .
```


### [Unstaging Changes](http://stackoverflow.com/questions/348170/undo-git-add-before-commit)

Maybe you accidentally staged some files that you don't want to commit.
```shell
$ git reset HEAD foo.js
$ git reset HEAD .
$ git config --global alias.unstage 'reset HEAD'
$ git unstage .
```


### [Commits](https://www.kernel.org/pub/software/scm/git/docs/git-commit.html)

Commit often. You can always squash down your commits before a push.
```shell
$ git commit -m "Fixed IE issues"
```

Want to automatically stage files that have been modified and deleted, but new files you haven't told git about will be unaffected? Pass the `-a` or `--all` option flag:
```shell
$ git commit -am "Fixed IE issues"
```


### [Undoing Commits](https://www.kernel.org/pub/software/scm/git/docs/git-reset.html)

The following command will undo your most recent commit and put those changes back into staging, so you don't lose any work:
```shell
$ git reset --soft HEAD~1
```

The next one will completely delete the commit and throw away any changes. Be absolutely sure this is what you want:
```shell
$ git reset --hard HEAD~1
```


### [Squashing Commits](https://www.kernel.org/pub/software/scm/git/docs/git-rebase.html)

Maybe you have 4 commits, but you haven't pushed anything yet and you want to put everything into one commit so your boss doesn't have to read a bunch of garbage during code review.
```shell
$ git rebase -i HEAD~4
```

An interactive text file is displayed. You'll see the word "pick" to the left of each commit. Leave the one at the top alone and replace all the others with "s" for squash, save and close the file. This will display another interactive window where you can update your commit messages into one new commit message. I like to use "f" instead of "s", because I usually work in such a way that I name my first commit appropriately from the get-go. "f" just skips the 2nd interactive file and uses the first commit message.


### [Pushing](https://www.kernel.org/pub/software/scm/git/docs/git-push.html)

Push a local branch for the first time:
```shell
$ git push --set-upstream origin <branch>
$ git push
```

Push a local branch to a different remote branch:
```shell
$ git push origin <local_branch>:<remote_branch>
```

Use the `-f` option flag to force it.


### [Undo Last Push](https://www.kernel.org/pub/software/scm/git/docs/git-reset.html)

Some would say this is bad practice. Once you push something you shouldn't overwrite those changes. Instead, you're supposed to create a new commit that reverts the changes in the last one. So, technically, you shouldn't do this, but... you can?
```shell
$ git reset --hard HEAD~1 && git push -f origin master
```


### [Fetching](https://www.kernel.org/pub/software/scm/git/docs/git-fetch.html)

Fetch changes from upstream:
```shell
$ git fetch upstream
```

Fetch changes from both origin and upstream in the same shot:
```shell
$ git fetch --multiple origin upstream
```


### [Merging](https://www.kernel.org/pub/software/scm/git/docs/git-merge.html)

To be honest, I haven't used this command in quite some time. In my experience, it has created merge bubbles that have overwritten mine or others' code. For a better workflow, refer to rebasing, below.

Nonetheless, here's how you merge-in changes from origin's `feature_x` branch:
```shell
$ git fetch origin
$ git merge origin/feature_x
```


### [Pulling](https://www.kernel.org/pub/software/scm/git/docs/git-pull.html)

Pulling is just doing a fetch followed by a merge. If you know your branch is clean (e.g., master branch), go ahead and get the latest changes. There will be no merge conflicts as long as your branch is clean.
```shell
$ git pull origin/feature_x
```


### [Rebasing](https://www.kernel.org/pub/software/scm/git/docs/git-rebase.html)

Rebasing is a way of rewriting history. In place of merge, what this does is stacks your commits on top of commits that are already pushed up. In this case, you want to stack your commits on top of `origin/feature_x`:
```shell
$ git fetch origin
$ git rebase origin/feature_x
```

If you already have a local branch set to track `feature_x` then just do:
```shell
$ git rebase feature_x
```

Would you like to fetch, merge and then stack your changes on top, all in one shot? You can! If you have tracking setup on the current branch, just do:
```shell
$ git pull --rebase
```

Another great use of rebasing is just rewriting commit messages. To get an interactive text editor for the most recent commit, do:
```shell
$ git rebase -i HEAD~1
```

Now, you can replace "pick" with "r" and just change the commit message.


### [Manually Set Tracking](https://www.kernel.org/pub/software/scm/git/docs/git-config.html)

Perhaps you forgot to setup tracking when you pulled down a remote branch. No worries:
```shell
$ git config branch.<local_branch>.remote origin
$ git config branch.<local_branch>.merge refs/heads/<remote_branch>
```


### [Deleting Branches](https://www.kernel.org/pub/software/scm/git/docs/git-branch.html)

Delete a local branch:
```shell
$ git branch -d <local_branch>
```

Use the `-D` option flag to force it.

Delete a remote branch on origin:
```shell
$ git push origin :<remote_branch>
```


### [Stashing](https://www.kernel.org/pub/software/scm/git/docs/git-stash.html)

Sometimes you need to stash your changes so you can be on a clean branch or maybe because you want to go back and try something before you make a commit with these changes. Here's how you do a stash:
```shell
$ git stash
```

Now, if you want to unstash those changes and bring them back into your working directory:
```shell
$ git stash pop
```

Or maybe you want to unstash your changes without popping them off the stack. In other words, you might want to apply these stashed changes multiple times. To do this:
```shell
$ git stash apply
```

For a list of stashes:
```shell
$ git stash list
```

And to apply a specific stash from that list (e.g., stash@{3}):
```shell
$ git stash apply stash@{3}
```


### [Checkout as CRLF, Commit as LF](https://www.kernel.org/pub/software/scm/git/docs/git-config.html)
```shell
$ git config --global core.autocrlf true
```


## Git Bash

Once you're comfortable with what the above commands are doing, you might want to create some shortcuts for Git Bash. This allows you to work a lot faster by doing complex tasks in really short commands.

Refer to my [.bashrc Gist](https://gist.github.com/jedmao/1deb357e54b3daf5856c#file-bashrc) for a good list of useful shortcuts.