Get your server issues fixed by our experts for a price starting at just 25 USD/Hour. Click here to register and open a ticket with us now!

Author Topic: Git Cheat Sheet  (Read 9519 times)

0 Members and 1 Guest are viewing this topic.


  • Guest
Git Cheat Sheet
« on: November 18, 2018, 06:39:55 am »
Git is a version-control system for tracking changes in computer files and coordinating work on those files among multiple people. It is primarily used for source-code management in software development, but it can be used to keep track of changes in any set of files.

Set Up and Initialization

Check your Git version with the following command, which will also confirm that Git is installed.
Code: [Select]
git --version
You can initialize your current working directory as a Git repository with init.
Code: [Select]
git init
To copy an existing Git repository hosted remotely, you’ll use git clone with the repo’s URL or server location (in the latter case you will use ssh).

Code: [Select]
git clone
Show your current Git directory’s remote repository.
Code: [Select]
git remote
For a more verbose output, use the -v flag.
Code: [Select]
git remote -v
Add the Git upstream, which can be a URL or can be hosted on a server (in the latter case, connect with ssh).
Code: [Select]
git remote add upstream


When you’ve modified a file and have marked it to go in your next commit, it is considered to be a staged file.

Check the status of your Git repository, including files added that are not staged, and files that are staged.
Code: [Select]
git status
To stage modified files, use the add command, which you can run multiple times before a commit. If you make subsequent changes that you want included in the next commit, you must run add again.

You can specify the specific file with add.
Code: [Select]
git add
With . you can add all files in the current directory including files that begin with a ..
Code: [Select]
git add .
You can remove a file from staging while retaining changes within your working directory with reset.
Code: [Select]
git reset


Once you have staged your updates, you are ready to commit them, which will record changes you have made to the repository.

To commit staged files, you’ll run the commit command with your meaningful commit message so that you can track commits.
Code: [Select]
git commit -m "Commit message"
You can condense staging all tracked files with committing them in one step.
Code: [Select]
git commit -am "Commit message"
If you need to modify your commit message, you can do so with the --amend flag.
Code: [Select]
git commit --amend -m "New commit message"


A branch in Git is a movable pointer to one of the commits in the repository, it allows you to isolate work and manage feature development and integrations.

List all current branches with the branch command. An asterisk (*) will appear next to your currently active branch.
Code: [Select]
git branch
Create a new branch. You will remain on your currently active branch until you switch to the new one.
Code: [Select]
git branch new-branch
Switch to any existing branch and check it out into your current working directory.
Code: [Select]
git checkout another-branch
You can consolidate the creation and checkout of a new branch by using the -b flag.
Code: [Select]
git checkout -b new-branch
Rename your branch name.
Code: [Select]
git branch -m current-branch-name new-branch-name
Merge the specified branch’s history into the one you’re currently working in.
Code: [Select]
git merge branch-name
Abort the merge, in case there are conflicts.
Code: [Select]
git merge --abort
You can also select a particular commit to merge with cherry-pick with the string that references the specific commit.
Code: [Select]
git cherry-pick f7649d0
When you have merged a branch and no longer need the branch, you can delete it.
Code: [Select]
git branch -d branch-name
If you have not merged a branch to master, but are sure you want to delete it, you can force delete a branch.
Code: [Select]
git branch -D branch-name

Collaborate and Update

To download changes from another repository, such as the remote upstream, you’ll use fetch.
Code: [Select]
git fetch upstream
Merge the fetched commits.
Code: [Select]
git merge upstream/master
Push or transmit your local branch commits to the remote repository branch.
Code: [Select]
git push origin master
Fetch and merge any commits from the tracking remote branch.
Code: [Select]
git pull


Display the commDisplay the commit history for the currently active branch.
Code: [Select]
git log
Show the commits that changed a particular file. This follows the file regardless of file renaming.
Code: [Select]
git log --follow
Show the commits that are on one branch and not on the other. This will show commits on a-branch that are not on b-branch.
Code: [Select]
git log a-branch..b-branch
Look at reference logs (reflog) to see when the tips of branches and other references were last updated within the repository.
Code: [Select]
git reflog
Show any object in Git via its commit string or hash in a more human-readable format.
Code: [Select]
git show de754f5

Show Changes

The git diff command shows changes between commits, branches, and more.

Compare modified files that are on the staging area.
Code: [Select]
git diff --staged
Display the diff of what is in a-branch but is not in b-branch.
Code: [Select]
git diff a-branch..b-branch
Show the diff between two specific commits.
Code: [Select]
git diff 61ce3e6..e221d9c


Sometimes you’ll find that you made changes to some code, but before you finish you have to begin working on something else. You’re not quite ready to commit the changes you have made so far, but you don’t want to lose your work. The git stash command will allow you to save your local modifications and revert back to the working directory that is in line with the most recent HEAD commit.

Stash your current work.
Code: [Select]
git stash
See what you currently have stashed.
Code: [Select]
git stash list
Your stashes will be named stash@{0}, stash@{1}, and so on.

Show information about a particular stash.
Code: [Select]
git stash show stash@{0}
To bring the files in a current stash out of the stash while still retaining the stash, use apply.
Code: [Select]
git stash apply stash@{0}
If you want to bring files out of a stash, and no longer need the stash, use pop.
Code: [Select]
git stash pop stash@{0}
If you no longer need the files saved in a particular stash, you can drop the stash.
Code: [Select]
git stash drop stash@{0}
If you have multiple stashes saved and no longer need to use any of them, you can use clear to remove them.
Code: [Select]
git stash clear

Ignoring Files

If you want to keep files in your local Git directory, but do not want to commit them to the project, you can add these files to your .gitignore file so that they do not cause conflicts.

Use a text editor such as nano to add files to the .gitignore file.
Code: [Select]
nano .gitignore


A rebase allows us to move branches around by changing the commit that they are based on. With rebasing, you can squash or reword commits.

You can start a rebase by either calling the number of commits you have made that you want to rebase (5 in the case below).
Code: [Select]
git rebase -i HEAD~5
Alternatively, you can rebase based on a particular commit string or hash.
Code: [Select]
git rebase -i 074a4e5
Once you have squashed or reworded commits, you can complete the rebase of your branch on top of the latest version of the project’s upstream code.
Code: [Select]
git rebase upstream/master

Sometimes, including after a rebase, you need to reset your working tree. You can reset to a particular commit, and delete all changes, with the following command.

Code: [Select]
git reset --hard 1fc6665
To force push your last known non-conflicting commit to the origin repository, you’ll need to use --force.
Code: [Select]
git push --force origin master
To remove local untracked files and subdirectories from the Git directory for a clean working branch, you can use git clean.
Code: [Select]
git clean -f -d
If you need to modify your local repository so that it looks like the current upstream master (that is, there are too many conflicts), you can perform a hard reset.
Code: [Select]
git reset --hard upstream/master