Important Git terminologies that every developer should know

Hey guys in this post we will discuss Git terminologies that every developer should know


Git terminologies

Following are the important Git terminologies –

  • Branch
  • Checkout
  • Cherry picking
  • Clone
  • Fetch
  • Head
  • Origin
  • Pull/Pull request
  • Push
  • Index
  • Master
  • Merge
  • Remote
  • Repository
  • Git fork


A branch is a version of the repository that diverges from the main working project.


The git checkout command is used to switch branches in a repository. git checkout master would drop you back into master.

Cherry picking

Cherry picking cherry-picking in git is meant to apply some commit from one branch into another branch.


The git clone is used to make a copy of the target repository or clone it.


It is used to fetch branches and tags from one or more other repositories, along with the objects necessary to complete their histories.


HEAD is the representation of the last commit in the current checkout branch. We can think of the head like a current branch.


It is used instead of that original repository URL to make referencing much easier.

Pull request

The term pull is used to receive data from Github. It fetches and merges changes on the remote server to your working directory. The git pull command is used to make a git pull.


The push term refers to upload local repository content to a remote repository. Pushing is an act of transfer commits from your local repository to a remote repository.


The git index is a staging area between the working directory and repository. It is used as the index to build up a set of changes that you want to commit together.


Master is a naming convention for git branch. It means that “master” is repository’s “default” branch.


Merging is a process to put a forked history back together.


In git, the term remote is concerned with the remote repository. It is a shared repository that all team members use to exchange their changes.


It contains the collection of the file as well as the history of changes made to those files. Repositories in git is considered as your project folder.

Git fork

A fork is a rough copy of a repository. Forking a repository allows you to freely test and debug with changes without affecting the original project.

Bushan Sirgur

Hey guys, I am Bushan Sirgur from Banglore, India. Currently, I am working as an Associate project in an IT company.

Leave a Reply