Git vs Github/Bitbucket/Gitlab

Jinna Balu
2 min readJun 17, 2020


git vs GitHub | git vs Bitbucket | git vs Gitlab

Is there a thing that we can compare git with GitHub? Is this possible to compare? According to my understanding, there is no such comparison between git and Github/Bitbucket/Gitlab. Why? Just follow with me on this post

git vs GitHub | git vs Bitbucket | git vs Gitlab


Git is the source control management tool, which manages files by tracking the following

  • Who modified when
  • Which file has changes and what is the change
  • What file added and what file deleted

Git tracking systems helps us to check with the modifications done by the individual user’s commit id and what is the change made with commit.

Github, Bitbucket, Gitlab

Git provides us to create the local repository to track the change of the single user who created the local git server. We lose these changes or files or commit history when the system gets crashed. We can’t recover from the lost code or repository created locally.

To overcome this issue we can host the git on the remote machine and sync the local repository with the remote repository, that is where these Github, Bitbucket, Gitlab come in place. There is no such thing to compare git with Github. Github/Gitlab/Bitbucket provides the cloud hosting service to manage the repositories.

Local git can be connected to the remote git server which is hosted git as service, these are publically available for the creation of the repository and push the changes from local to the remote repository.

So we call Github/Bitbucket/Gitlab as git host providers. These hosted services allow us to

  • Create the repository in remote git server
  • Initialize the local git repository and add the remote repository URL
  • Give access to multiple contributors
  • Each contributor can Clone the repository to the local machine
  • Pull changes when other contributors update the remote repository
  • Push changes to the remote repository
  • Reset Back to the commit history as required

There is a centralized code in the remote repository, but along with that it also distributed over multiple contributor’s machines as a local repository, it is decentralized too.

When multiple contributors pushing the code there is a chance that we face conflicts when two individuals modified the same file. This is when the branching concept comes in place. We’ll understand that in Git Branching for Contributors.



Jinna Balu

Devops Architect, Practising Natural Farming