<p>Git is a specific open-source version control system created by Linus Torvalds in 2005. Specifically, Git is a distributed version control system, which means that the entire codebase and history are available on every developer’s computer, which allows for easy branching and merging. Why use something like Git? Say you and a coworker are both updating pages on the same website. You make your changes, save them, and upload them back to the website. So far, so good. The problem comes when your coworker is working on the same page as you at the same time. One of you is about to have your work overwritten and erased.</p><p><br></p><p><br></p><p>A version control application like Git keeps that from happening. You and your coworker can each upload your revisions to the same page, and Git will save two copies. Later, you can merge your changes together without losing any work along the way. You can even revert to an earlier version at any time because Git keeps a “snapshot” of every change ever made.</p><p><br></p><p>Read more about why git is the developer's favorite <a href="https://blogue.tech/feeds/git:developer's-favourite" rel="noopener noreferrer" target="_blank">here</a>.</p><p><br></p><p>Let's list and shortly explain the important git commands for every developer:</p><p><br></p><h2>Check your Git configuration:</h2><p>The command below returns a list of information about your git configuration including user name and email:</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-built_in">config</span> -l
</pre><h2><br></h2><h2>Setting up your Git username:</h2><p>With the command below you can configure your user name:</p><pre class="ql-syntax" spellcheck="false">git config --<span class="hljs-built_in">global</span> user.name <span class="hljs-string">"sujanchhetri"</span>
</pre><h2><br></h2><h2>Setting up your Git user email:</h2><p>This command lets you set up the user email address you'll use in your commits.</p><pre class="ql-syntax" spellcheck="false">git config --<span class="hljs-built_in">global</span> user.email <span class="hljs-string">"hello@sujanchhetri.dev"</span>
</pre><h2><br></h2><h2>Caching your login credentials in Git:</h2><p>You can store login credentials in the cache so you don't have to type them in each time. Just use this command:</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-built_in">config</span> <span class="hljs-comment">--global credential.helper cache</span>
</pre><h2><br></h2><h2>Initializing a Git repo:</h2><p>Everything starts from here. The first step is to initialize a new Git repo locally in your project root. You can do so with the command below:</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-keyword">init</span>
</pre><h2><br></h2><h2>Adding a file to the staging area in Git:</h2><p>The command below will add a file to the staging area. Just replace the filename with the name of the file you want to add to the staging area.</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-keyword">add</span> filename
</pre><h2><br></h2><h2>Adding all files in the staging area in Git:</h2><p>If you want to add all files in your project to the staging area, you can use a '.' and every file will be added for you.</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-keyword">add</span> .
</pre><h2><br></h2><h2>Adding only certain files to the staging area in Git:</h2><p>With the asterisk in the command below, you can add all files. Example: File start with 'hello' in the staging area.</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-keyword">add</span> hello*
</pre><h2><br></h2><h2>Checking a repository's status in Git:</h2><p>This command will show the status of the current repository including staged, unstaged, and untracked files.</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-built_in">status</span>
</pre><h2><br></h2><h2>Commit changes in the editor in Git:</h2><p>This command will open a text editor in the terminal where you can write a full commit message.</p><p>A commit message is made up of a short summary of changes, an empty line, and a full description of the changes after it.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> commit
</pre><h2><br></h2><h2>Commit changes with a message in Git:</h2><p>You can add a commit message without opening the editor. This command lets you only specify a short summary for your commit message.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> commit -m <span class="hljs-string">"commit message"</span>
</pre><h2><br></h2><h2>Commit changes (and skip the staging area) in Git:</h2><p>You can add and commit tracked files with a single command by using the -a and -m options.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> commit -a -m <span class="hljs-string">"commit message"</span>
</pre><h2><br></h2><h2>Commit history in Git:</h2><p>This command shows the commit history for the current repository:</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-built_in">log</span>
</pre><h2><br></h2><h2>Commit history including changes in Git:</h2><p>This command shows the commit's history including all files and their changes:</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-built_in">log</span> -p
</pre><h2><br></h2><h2>See a specific commit in Git:</h2><p>This command shows a specific commit.</p><p>Replace commit-id with the id of the commit that you find in the commit log after the word commit.</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-keyword">show</span> <span class="hljs-keyword">commit</span>-<span class="hljs-keyword">id</span>
</pre><h2><br></h2><h2>See log stats in Git:</h2><p>This command will cause the Git log to show some statistics about the changes in each commit, including line(s) changed and file names.</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-built_in">log</span> --<span class="hljs-built_in">stat</span>
</pre><h2><br></h2><h2>See changes made before committing them using "diff" in Git:</h2><p>You can pass a file as a parameter to only see changes on a specific file.</p><p> git diff shows only unstaged changes by default.</p><p>We can call diff with the --staged flag to see any staged changes.</p><pre class="ql-syntax" spellcheck="false">git diff
git diff all_checks.py
git diff --staged
</pre><h2><br></h2><h2>See changes using "git add -p":</h2><p>This command opens a prompt and asks if you want to stage changes or not, and includes other options.</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-keyword">add</span> -p
</pre><h2><br></h2><h2>Remove tracked files from the current working tree in Git:</h2><p>This command expects a commit message to explain why the file was deleted.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> rm filename
</pre><h2><br></h2><h2>Rename files in Git:</h2><p>This command stages the changes, then it expects a commit message.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> mv oldfile newfile
</pre><h2><br></h2><h2>Ignore files in Git:</h2><p>Create a  file and name it ".gitignore" and add filenames inside it to ignore while adding it to a git branch.</p><h2><br></h2><h2>Revert unstaged changes in Git:</h2><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> checkout filename
</pre><h2><br></h2><h2>Revert staged changes in Git:</h2><p>You can use the -p option flag to specify the changes you want to reset.</p><pre class="ql-syntax" spellcheck="false">git&nbsp;<span class="hljs-keyword">reset</span> <span class="hljs-keyword">HEAD</span> filename
git <span class="hljs-keyword">reset</span> <span class="hljs-keyword">HEAD</span> -p
</pre><h2><br></h2><h2>Amend the most recent commit in Git:</h2><p>git commit --amend allows you to modify and add changes to the most recent commit.</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-keyword">commit</span> <span class="hljs-comment">--amend</span>
</pre><p>!!Note!!: fixing up a local commit with amend is great and you can push it to a shared repository after you've fixed it. But you should avoid amending commits that have already been made public.</p><p><br></p><h2>Rollback the last commit in Git:</h2><p>git revert will create a new commit that is the opposite of everything in the given commit.</p><p> We can revert the latest commit by using the head alias like this:</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> revert HEAD
</pre><h2><br></h2><h2>Rollback an old commit in Git:</h2><p>You can revert an old commit using its commit id. This opens the editor so you can add a commit message.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> revert comit_id_here
</pre><h2><br></h2><h2>Creating a new branch in Git:</h2><p>By default, you have one branch, the main branch. With this command, you can create a new branch. Git won't switch to it automatically – you will need to do it manually with the next command.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> branch branch_name
</pre><h2><br></h2><h2>Switching to a newly created branch in Git:</h2><p>When you want to use a different or a newly created branch you can use this command:</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> checkout branch_name
</pre><h2><br></h2><h2>List branches in Git:</h2><p>You can view all created branches using the git branch command. It will show a list of all branches and mark the current branch with an asterisk and highlight it in green.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> branch
</pre><h2><br></h2><h2>Creating a branch in Git and switch to it immediately:</h2><p>In a single command, you can create and switch to a new branch right away.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> checkout -b branch_name
</pre><h2><br></h2><h2>Deleting a branch in Git:</h2><p>When you are done working with a branch and have merged it, you can delete it using the command below:</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> branch -d branch_name
</pre><h2><br></h2><h2>Merging two branches in Git:</h2><p>To merge the history of the branch you are currently in with the branch_name, you will need to use the command below:</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> merge branch_name
</pre><h2><br></h2><h2>Showing the commit log as a graph in Git:</h2><p>We can use --graph to get the commit log to show as a graph. Also,</p><p> --oneline will limit commit messages to a single line.</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-built_in">log</span> <span class="hljs-comment">--graph --oneline</span>
</pre><h2><br></h2><h2>Showing the commit log as a graph of all branches in Git:</h2><p>Does the same as the command above, but for all branches.</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-built_in">log</span> <span class="hljs-comment">--graph --online --all</span>
</pre><h2><br></h2><h2>Aborting a conflicting merge in Git:</h2><p>If you want to throw a merge away and start over, you can run the following command:</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-keyword">merge</span> <span class="hljs-comment">--abort</span>
</pre><h2><br></h2><h2>Adding a remote repository in Git</h2><p>This command adds a remote repository to your local repository (just replace https://repo_name with your remote repo URL).</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-keyword">add</span> remote https:<span class="hljs-comment">//repo_name</span>
</pre><h2><br></h2><h2>See remote URLs in Git:</h2><p>You can see all remote repositories for your local repository with this command:</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> remote -v
</pre><h2><br></h2><h2>Get more info about a remote repo in Git:</h2><p>Just replace origin with the name of the remote obtained by</p><p> running the git remote -v command.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> remote show origin
</pre><h2><br></h2><h2>Push changes to a remote repo in Git:</h2><p>When all your work is ready to be saved on a remote repository, you can push all changes using the command below:</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> push
</pre><h2><br></h2><h2>Pull changes from a remote repo in Git:</h2><p>If other team members are working on your repository, you can retrieve the latest changes made to the remote repository with the command below:</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> pull
</pre><h2><br></h2><h2>Check remote branches that Git is tracking:</h2><p>This command shows the name of all remote branches that Git is tracking for the current repository:</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> branch -r

</pre><h2><br></h2><h2>Fetch remote repo changes in Git:</h2><p>This command will download the changes from a remote repo but will not perform a merge on your local branch (as git pull does that instead).</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> fetch
</pre><h2><br></h2><h2>Check the current commits log of a remote repo in Git</h2><p>Commit after commit, Git builds up a log. You can find out the remote repository log by using this command:</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-built_in">log</span> origin/main
</pre><h2><br></h2><h2>Merge a remote repo with your local repo in Git:</h2><p>If the remote repository has changes you want to merge with your local, then this command will do that for you:</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-keyword">merge</span> origin/<span class="hljs-keyword">main</span>
</pre><h2><br></h2><h2>Getting the contents of remote branches in Git without automatically merging:</h2><p>This lets you update the remote without merging any content into the</p><p> local branches. You can call git merge or git checkout to do the merge.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> remote update
</pre><h2><br></h2><h2>Push a new branch to a remote repo in Git:</h2><p>If you want to push a branch to a remote repository you can use the command below. Just remember to add -u to create the branch upstream:</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> push -u origin branch_name

</pre><h2><br></h2><h2>Remove a remote branch in Git:</h2><p>If you no longer need a remote branch you can remove it using the command below:</p><pre class="ql-syntax" spellcheck="false">git <span class="hljs-keyword">push</span> --<span class="hljs-keyword">delete</span> origin branch_name
</pre><h2><br></h2><h2>Using Git rebase:</h2><p>You can transfer completed work from one branch to another using git-rebase.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> rebase branch_name
</pre><p>Git Rebase can get really messy if you don't do it properly. Before using this command I suggest that you re-read the official documentation <a href="https://git-scm.com/book/it/v2/Git-Branching-Rebasing" rel="noopener noreferrer" target="_blank">here</a></p><h2><br></h2><h2>Running rebase interactively in Git:</h2><p>You can run git rebase interactively using the -i flag.</p><p> It will open the editor and present a set of commands you can use.</p><pre class="ql-syntax" spellcheck="false">git rebase -i master
- p, pick = <span class="hljs-keyword">use</span> <span class="hljs-keyword">commit</span>
- r, reword = <span class="hljs-keyword">use</span> <span class="hljs-keyword">commit</span>, but edit the <span class="hljs-keyword">commit</span> message
- e, edit = <span class="hljs-keyword">use</span> <span class="hljs-keyword">commit</span>, but <span class="hljs-keyword">stop</span> <span class="hljs-keyword">for</span> amending
- s, squash = <span class="hljs-keyword">use</span> <span class="hljs-keyword">commit</span>, but meld <span class="hljs-keyword">into</span> previous <span class="hljs-keyword">commit</span>
- f, fixup = <span class="hljs-keyword">like</span> squash, but discard this <span class="hljs-keyword">commit</span> <span class="hljs-keyword">log</span> message
- x, exec = run command (the rest <span class="hljs-keyword">of</span> the line) <span class="hljs-keyword">using</span> shell
- d, <span class="hljs-keyword">drop</span> = remove <span class="hljs-keyword">commit</span>
</pre><h2><br></h2><h2>Force a push request in Git:</h2><p>This command will force a push request. This is usually fine for pull request branches because nobody else should have cloned them.</p><p> But this isn't something that you want to do with public repos.</p><pre class="ql-syntax" spellcheck="false"><span class="hljs-attribute">git</span> push -f
</pre><p><br></p><p>Happy Coding ...</p>

Must know Git Commands for Every Developer

Related blogs

About us: