What is GitHub? Cloud Hosting for Git, GitHub vs GitLab vs Bitbucket

Every lesson so far in this course has focused on Git itself — the version control tool running entirely on your own machine. GitHub is something different: a cloud-based hosting platform built around Git, adding collaboration features, a web interface, and a social layer on top of the plain command-line tool you already know. Understanding exactly where Git ends and GitHub begins clears up one of the most common points of confusion for beginners entering the world of collaborative software development.

Learning Objectives

• Define GitHub and explain its relationship to Git.
• Identify the core features GitHub adds on top of plain Git.
• Compare GitHub to its main competitors, GitLab and Bitbucket.
• Understand why a remote hosting platform is useful even though Git itself is fully distributed.

Key Terms to Know Before Learning What GitHub Is

• GitHub: A cloud-based platform for hosting Git repositories, adding a web interface, collaboration tools (pull requests, issues), and social features on top of Git.
• Remote repository: A copy of a Git repository hosted on a server (such as GitHub) rather than on a local machine, used as a shared point of synchronization between collaborators.
• Pull request (PR): A GitHub feature that proposes merging changes from one branch into another, with built-in support for code review and discussion before the merge happens.
• GitLab: A competing platform to GitHub, offering similar Git hosting and collaboration features, along with a strong focus on integrated CI/CD pipelines.
• Bitbucket: A competing platform to GitHub, made by Atlassian, notable for its tight integration with other Atlassian products like Jira and Trello.

How GitHub Actually Relates to Git

Recall from Module 1 that Git is a distributed version control system — every clone contains the complete project history, and Git itself has no inherent requirement for a central server at all. So why does GitHub exist, and why is it so central to modern software development?

GitHub takes the raw, powerful, but fundamentally command-line-oriented tool that is Git, and wraps it in a hosted, web-based platform that solves problems Git alone doesn't address:

1. **A reliable, always-available shared location.** While Git doesn't strictly require a central server, teams still need one agreed-upon, reliably available place to push to and pull from. GitHub provides that as a hosted service, so no individual team member's laptop needs to act as the 'source of truth'.
2. **A web interface for browsing code, history, and issues** without needing to run Git commands at all — useful for stakeholders, reviewers, or anyone who just needs to look at something quickly.
3. **Pull requests**, GitHub's mechanism for proposing, discussing, and reviewing a set of changes before they're merged — adding a structured, auditable collaboration and code-review layer on top of Git's raw `merge` command.
4. **Issue tracking**, letting teams log bugs, feature requests, and tasks directly alongside the code they relate to.
5. **Social and discovery features** — profiles, stars, followers, and trending repositories — which have made GitHub as much a professional networking platform as a hosting service, particularly within open source.

It's worth being precise about terminology here: **Git and GitHub are not the same thing.** Git is the version control software itself, usable entirely offline with no account of any kind. GitHub is one company's specific product for hosting Git repositories in the cloud and adding collaboration tooling on top. You could use Git for your entire career without ever touching GitHub — but in practice, GitHub (or a direct competitor) has become the near-universal standard for how teams and open-source projects host and collaborate around their Git repositories.

GitHub's two main competitors follow the same basic model — hosting Git repositories with added collaboration tooling — but with different areas of emphasis. **GitLab** is particularly known for its strong, tightly integrated CI/CD (continuous integration/deployment) pipeline features built directly into the platform, and offers a notable open-source, self-hostable version that some companies run on their own infrastructure rather than in GitLab's cloud. **Bitbucket**, made by Atlassian, is most commonly chosen by teams already using other Atlassian products like Jira (issue tracking) and Trello (project boards), due to its tight, native integration with that ecosystem. All three platforms fundamentally host the same kind of Git repositories underneath — a repository created on GitHub could, in principle, be pushed to GitLab or Bitbucket instead, since Git itself doesn't care which hosting platform is on the other end.

GitHub vs Git: Visual Overview

Draw a simple layered diagram. Bottom layer: 'Git — the version control engine (runs locally, works offline, no account needed)'. Middle layer, sitting on top: 'GitHub / GitLab / Bitbucket — cloud hosting platforms for Git repositories'. Top layer: 'Features added on top of Git: web interface, pull requests, issue tracking, CI/CD, social profiles'. Draw an arrow from a laptop icon (local Git repo) up to a cloud icon labeled 'origin' (the hosted remote on GitHub), labeled 'git push / git pull — synchronizing between local Git and a hosting platform'.

GitHub vs GitLab vs Bitbucket: Side-by-Side Comparison

Platform	GitHub	GitLab
Primary strength	Largest community, dominant for open source	Strong built-in CI/CD pipelines
Self-hostable version	GitHub Enterprise (paid)	GitLab Community Edition (free, open-source)
Owned by	Microsoft	GitLab Inc.
Notable ecosystem	GitHub Actions, GitHub Copilot, largest OSS discovery	Integrated DevOps platform (issues, CI/CD, registry)

Confirming Git Is Configured to Work With GitHub

# Confirm Git is installed and check current remote configuration (none yet, for a new project)
git --version
git remote -v
# (no output yet — this repository has no remote configured)

# GitHub, GitLab, and Bitbucket all provide a URL once a repository is created there,
# used to connect your local repository to that hosted remote (covered in the 'git remote' lesson):
# https://github.com/username/my-project.git
# https://gitlab.com/username/my-project.git
# https://bitbucket.org/username/my-project.git

Breaking Down the GitHub Remote Connection Example

`git remote -v` run on a brand-new local repository shows no output, confirming that Git itself has no inherent connection to any hosting platform — remotes are configured explicitly, not automatic. The three example URLs illustrate that GitHub, GitLab, and Bitbucket all provide a similar HTTPS-based address for connecting a local repository to a hosted one, since all three are ultimately just Git hosting platforms wrapping the same underlying protocol — the choice of platform doesn't change how Git itself works, only which web features and ecosystem you get on top of it.

How GitHub Is Used on Real Engineering Teams

• GitHub hosts the vast majority of the world's open-source projects, and a public GitHub profile with active contributions has become a de facto part of many software engineers' professional resumes.
• Companies choosing between GitHub, GitLab, and Bitbucket often base the decision on existing tooling — a team already using Jira and Trello may lean toward Bitbucket, while a team wanting integrated CI/CD out of the box may lean toward GitLab.
• GitHub Actions, GitHub's built-in automation feature, has become extremely popular for running tests, builds, and deployments automatically whenever code is pushed, directly competing with GitLab's native CI/CD pipelines.
• Enterprises with strict data residency or security requirements sometimes choose GitLab's self-hostable Community/Enterprise Edition or GitHub Enterprise Server, running the platform on their own infrastructure rather than in the vendor's cloud.

GitHub Interview Questions and Answers

Q1. Is GitHub the same thing as Git?

No. Git is the version control software itself — it runs locally, works fully offline, and requires no account. GitHub is a separate, cloud-based company and product that hosts Git repositories and adds collaboration features like pull requests, issue tracking, and a web interface on top of Git.

Q2. What core features does GitHub add on top of plain Git?

GitHub adds a reliable, shared hosting location for repositories, a web interface for browsing code and history without running Git commands, pull requests for structured code review before merging, issue tracking for logging bugs and tasks, and social/discovery features like profiles and stars.

Q3. How does GitHub differ from GitLab and Bitbucket at a high level?

All three host Git repositories and add similar collaboration tooling, but each emphasizes different strengths: GitHub has the largest community and open-source presence, GitLab is known for strong built-in CI/CD pipelines and a free self-hostable edition, and Bitbucket is most commonly chosen by teams already invested in Atlassian's Jira and Trello ecosystem.

GitHub Basics Quiz: Test Your Understanding

1. What is the correct relationship between Git and GitHub?

1. They are the same product with two different names
2. Git is the version control software; GitHub is a cloud platform that hosts Git repositories and adds collaboration features
3. GitHub is required to use Git at all
4. Git was created by GitHub

Answer: B. Git is the version control software; GitHub is a cloud platform that hosts Git repositories and adds collaboration features

Explanation: Git is fully usable offline with no account of any kind. GitHub is a separate hosting platform built around Git, adding a web interface and collaboration tooling on top.

2. Which platform is particularly known for strong, tightly integrated CI/CD pipelines and a free, self-hostable edition?

1. GitHub
2. GitLab
3. Bitbucket
4. None of them offer CI/CD

Answer: B. GitLab

Explanation: GitLab is widely recognized for its integrated DevOps platform, including strong built-in CI/CD pipeline support, and for offering a free, open-source, self-hostable Community Edition.

3. Which platform is most commonly chosen by teams already using Jira and Trello?

1. GitHub
2. GitLab
3. Bitbucket
4. SourceForge

Answer: C. Bitbucket

Explanation: Bitbucket, made by Atlassian, integrates tightly and natively with other Atlassian products like Jira and Trello, making it a natural choice for teams already using that ecosystem.

Common Mistakes Beginners Make About GitHub

• Using 'Git' and 'GitHub' interchangeably in conversation or in writing, which can cause real confusion about what's actually being discussed.
• Assuming a GitHub account is required to use Git at all — Git works fully offline and independently of any hosting platform.
• Believing GitHub, GitLab, and Bitbucket are fundamentally incompatible — they all host standard Git repositories, so the same project could technically be hosted on any of them.
• Choosing a hosting platform based on popularity alone, without considering a team's existing tooling ecosystem (like Jira or built-in CI/CD needs).

GitHub vs Git: Exam-Ready Quick Notes

• Git = the version control software (local, offline, no account needed). GitHub = a cloud platform hosting Git repositories with added features.
• GitHub adds: web interface, pull requests, issue tracking, social/discovery features.
• GitLab: known for strong integrated CI/CD and a free self-hostable edition.
• Bitbucket: known for tight integration with Atlassian's Jira and Trello.

What is GitHub: Key Takeaways

• GitHub is a hosting platform built around Git, not a replacement for or a requirement of Git itself.
• Pull requests, issue tracking, and a web interface are GitHub's core additions on top of Git's raw version control capabilities.
• GitHub, GitLab, and Bitbucket all fundamentally host the same kind of Git repositories, differing mainly in their surrounding ecosystem and emphasis.

Frequently Asked Questions About GitHub

Q1. Is GitHub the same as Git?

No. Git is version control software that runs on your own computer and works entirely offline. GitHub is a separate company's cloud platform that hosts Git repositories and adds features like a web interface, pull requests, and issue tracking on top of Git.

Q2. Do I need a GitHub account to use Git?

No. Git is fully functional without any account or internet connection. A GitHub account is only needed if you want to host your repository on GitHub specifically, to collaborate with others or back up your project in the cloud.

Q3. What is the main difference between GitHub, GitLab, and Bitbucket?

All three host Git repositories and offer similar collaboration features, but GitHub has the largest community and open-source presence, GitLab is known for strong built-in CI/CD pipelines and a free self-hostable version, and Bitbucket integrates tightly with Atlassian tools like Jira and Trello.

Q4. What is a pull request?

It's a feature on platforms like GitHub that lets you propose merging changes from one branch into another, with built-in support for discussion and code review before the merge actually happens.

Q5. Can a project hosted on GitHub be moved to GitLab or Bitbucket instead?

Yes, since all three platforms fundamentally host the same kind of standard Git repositories. A project can be pushed to a new remote on a different platform, since Git itself doesn't care which hosting service is on the other end of a connection.

Summary

GitHub is a cloud-based platform for hosting Git repositories, adding a web interface, pull requests, issue tracking, and social features on top of the plain, locally-run Git tool covered in earlier modules. Git itself requires no account and works fully offline; GitHub provides a reliable, shared hosting location plus collaboration tooling that Git alone doesn't offer. GitHub's main competitors, GitLab and Bitbucket, host the same kind of underlying Git repositories but differ in emphasis — GitLab for its strong built-in CI/CD and free self-hostable edition, and Bitbucket for its tight integration with Atlassian's Jira and Trello. Understanding this distinction between Git (the tool) and GitHub (one company's hosting product) is the essential foundation for this entire module on remote repositories.