Git Cheat Sheet – 50 Git Commands You Should Know

Git is a distributed version control system that helps developers collaborate on projects of any scale.

Linus Torvalds, the developer of the Linux kernel, created Git in 2005 to help control the Linux kernel’s development.

What is a Distributed Version Control System?

A distributed version control system is a system that helps you keep track of changes you’ve made to files in your project.

This change history lives on your local machine and lets you revert to a previous version of your project with ease in case something goes wrong.

Git makes collaboration easy. Everyone on the team can keep a full backup of the repositories they’re working on on their local machine. Then, thanks to an external server like BitBucket, GitHub or GitLab, they can safely store the repository in a single place.

This way, different members of the team can copy it locally and everyone has a clear overview of all changes made by the whole team.

Git has many different commands you can use. And I’ve found that these fifty are the ones I use the most often (and are therefore the most helpful to remember).

So I have written them down and thought it’d be nice to share them with the community. I hope you find them useful – Enjoy.

  • How to check your Git configuration
  • How to setup your Git username
  • How to setup your Git user email
  • How to cache your login credentials in Git
  • How to initialize a Git repo
  • How to add a file to the staging area in Git
  • How to add all files in the staging area in Git
  • How to add only certain files to the staging area in Git
  • How to check a repository’s status in Git
  • How to commit changes in the editor in Git:
  • How to commit changes with a message in Git
  • How to commit changes (and skip the staging area) in Git
  • How to see your commit history in Git
  • How to see your commit history including changes in Git
  • How to see a specific commit in Git
  • How to see log stats in Git
  • How to see changes made before committing them using “diff” in Git
  • How to see changes using “git add -p”
  • How to remove tracked files from the current working tree in Git
  • How to rename files in Git
  • How to ignore files in Git
  • How to revert unstaged changes in Git
  • How to revert staged changes in Git
  • How to amend the most recent commit in Git
  • How to rollback the last commit in Git
  • How to rollback an old commit in Git
  • How to create a new branch in Git
  • How to switch to a newly created branch in Git
  • How to list branches in Git
  • How to create a branch in Git and switch to it immediately
  • How to delete a branch in Git
  • How to merge two branches in Git
  • How to show the commit log as a graph in Git:
  • How to show the commit log as a graph of all branches in Git
  • How to abort a conflicting merge in Git
  • How to add a remote repository in Git
  • How to see remote URLs in Git
  • How to get more info about a remote repo in Git
  • How to push changes to a remote repo in Git
  • How to pull changes from a remote repo in Git
  • How to check remote branches that Git is tracking
  • How to fetch remote repo changes in Git
  • How to check the current commits log of a remote repo in Git
  • How to merge a remote repo with your local repo in Git
  • How to get the contents of remote branches in Git without automatically merging
  • How to push a new branch to a remote repo in Git
  • How to remove a remote branch in Git
  • How to use Git rebase
  • How to run rebase interactively in Git
  • How to force a push request in Git

#git #github #developer #programming

What is GEEK

Buddha Community

Git Cheat Sheet – 50 Git Commands You Should Know
Myriam  Rogahn

Myriam Rogahn


Basic Git Commands you need to Master

In this part you will get familiar with some basic Git commands. At the end of this blog you will be able to perform certain task like

  • Set up a folder as a Git repository
  • Perform basic Git operations on your Git repository

These are those commands you must conquer

Basic Git Commands

  • At any location on your computer, create a folder named git-test.
  • Open this git-test folder in your favorite editor.
  • Add a file named index.html to this folder, and add the following HTML code to this file:
<!DOCTYPE html>

<h1>Sab Batade Aapko</h1>

Initializing the folder as a Git repository

  • Go to the git-test folder in your cmd window/terminal and type the following command at the prompt to initialize the folder as a Git repository:
git init

this command will make a file named .git

#github #git #basic-git-commands #git-commands #git-status

7 Best Practices in GIT for Your Code Quality

There is no doubt that Git plays a significant role in software development. It allows developers to work on the same code base at the same time. Still, developers struggle for code quality. Why? They fail to follow git best practices. In this post, I will explain seven core best practices of Git and a Bonus Section.

1. Atomic Commit

Committing something to Git means that you have changed your code and want to save these changes as a new trusted version.

Version control systems will not limit you in how you commit your code.

  • You can commit 1000 changes in one single commit.
  • Commit all the dll and other dependencies
  • Or you can check in broken code to your repository.

But is it good? Not quite.

Because you are compromising code quality, and it will take more time to review codeSo overall, team productivity will be reduced. The best practice is to make an atomic commit.

When you do an atomic commit, you’re committing only one change. It might be across multiple files, but it’s one single change.

2. Clarity About What You Can (& Can’t) Commit

Many developers make some changes, then commit, then push. And I have seen many repositories with unwanted files like dll, pdf, etc.

You can ask two questions to yourself, before check-in your code into the repository

  1. Are you suppose to check-in all these files?
  2. Are they part of your source code?

You can simply use the .gitignore file to avoid unwanted files in the repository. If you are working on more then one repo, it’s easy to use a global .gitignore file (without adding or pushing). And .gitignore file adds clarity and helps you to keep your code clean. What you can commit, and it will automatically ignore the unwanted files like autogenerated files like .dll and .class, etc.

#git basics #git command #git ignore #git best practices #git tutorial for beginners #git tutorials

Rupert  Beatty

Rupert Beatty


Git Commands You Can Use To Dig Through Your Git History

In this short article, we’ll be exploring some quick  git commands that can help us in digging through our repositories’ history of commits. We’ll look at

  1. git log
  2. git shortlog
  3. git show
  4. git rev-list

#git #git-log #git-commands #git-history #aws

Madyson  Reilly

Madyson Reilly


Best Practices for Using Git

Git has become ubiquitous as the preferred version control system (VCS) used by developers. Using Git adds immense value especially for engineering teams where several developers work together since it becomes critical to have a system of integrating everyone’s code reliably.

But with every powerful tool, especially one that involves collaboration with others, it is better to establish conventions to follow lest we shoot ourselves in the foot.

At DeepSource, we’ve put together some guiding principles for our own team that make working with a VCS like Git easier. Here are 5 simple rules you can follow:

1. Make Clean, Single-Purpose Commits

Oftentimes programmers working on something get sidetracked into doing too many things when working on one particular thing — like when you are trying to fix one particular bug and you spot another one, and you can’t resist the urge to fix that as well. And another one. Soon, it snowballs and you end up with so many changes all going together in one commit.

This is problematic, and it is better to keep commits as small and focused as possible for many reasons, including:

  • It makes it easier for other people in the team to look at your change, making code reviews more efficient.
  • If the commit has to be rolled back completely, it’s far easier to do so.
  • It’s straightforward to track these changes with your ticketing system.

Additionally, it helps you mentally parse changes you’ve made using git log.

#open source #git #git basics #git tools #git best practices #git tutorials #git commit

Monty  Boehm

Monty Boehm


Top 35 Git Commands With Examples

Git commands are essential, and they help to manage your source code effectively. In this guide, you will learn Git commands from Beginners to Advanced level.

If you are a new or experienced developer, you have to use source control. And good chances are you are using Git to manage your source code.

And to use Git to its full potential, you need to know Git commands. Here you will learn the most helpful Git commands that will take you from one level to another.

To make this Git commands guide more helpful, I have divided the guide into three different sections: Basic, Intermediate, and Advanced Git commands.

This is an epic guide. And to make it more useful, I have added a Bonus section where you can download  51+ Git commands and a few more downloads to boost your productivity in Git.

Basic Git Commands

In this section, you will learn the essential Git commands. These basic Git commands are the foundation to learn more advanced commands.

Here are the nine useful Git commands.

1. git config

2. git version

3. git init

4. git clone

5. git add

6. git commit

7. git status

8. git branch

9. git checkout

10. git remote

11. git push

13. git fetch

14. git pull

15. git stash

16. git log

17. git shortlog

18. git show

19. git rm

20. git merge

21. git rebase

22. git bisect

23. git cherry-pick

24. git archive

26. git blame

27. git tag

28. git verify-commit

29. git verify-tag

30. git diff

31. git citool

32. git mv

33. git clean

34. git help

35. git whatchanged

#git #git commands #git commits #git tutorial