# GitHub, GitLab and Bitbucket

> The three big sites that host Git repos, and what each one adds to Git. How GitHub Issues tracks bugs, and how one line in a pull request closes one.

**Course:** [Git and GitHub](https://learn.benibix.com/learn/development-version-control)  
**Time:** 12 min

**After this lesson you can:**

- Say what a Git host adds to Git
- Compare GitHub, GitLab and Bitbucket
- Close an issue from a pull request

## What a Git host adds, and how the three differ

GitHub, GitLab and Bitbucket are websites that keep Git repos online, so a team has one shared copy to push to and pull from. They add what Git leaves out: a web page for each repo, a list of bugs and tasks, a place to review changes, and tests that run on each push. GitHub opened in 2008.

Git itself does none of this. It saves history and moves commits between copies. Everything with a button, a comment or an email comes from the host. That is why you can move to a new host by pushing the same repo to a new remote, and keep every commit.

GitHub is the biggest of the three. Most public projects live there, so it is the site you will clone from most often. Its request to join a branch is called a pull request. Its system for running tests on each push is called GitHub Actions.

GitLab does the same job, with some words changed. A pull request there is called a merge request. Its system for running tests is built into the same product. A company can also run all of GitLab on its own servers, instead of on GitLab's site.

Bitbucket is made by the same firm as Jira, the task tracker. Its big draw is that link. A branch or commit that names a Jira task, such as SHOP-42, shows up on that task in Jira. Teams that already plan their work in Jira often pick Bitbucket for that reason.

GitHub Issues is the to-do list beside the code. Each issue gets a number, a title and a thread for talk. You can label it, give it to a person and put it on a board. GitLab has its own version, and Bitbucket teams often use Jira for the same job.

An issue can close itself. Write Closes #42 in a pull request, and issue 42 closes the moment that request is merged. Fixes and Resolves work the same way. It only works when the request is merged into the repo's default branch, which is usually main.

People often pick a host on its list of features. The lists are close enough that they rarely decide much. What matters more is what your team already uses. Where do your other repos live? Where do you track tasks? Which one does your company already pay for?

## The three Git hosts

| Host | A request to merge is called | Known for |
| --- | --- | --- |
| GitHub | Pull request | Most public projects live here |
| GitLab | Merge request | Tests built in, and you can run it yourself |
| Bitbucket | Pull request | Its link to Jira |

## Which one to pick

1. **GitHub.** When you work in public, or want the most people and tools to already know your host.
2. **GitLab.** When your company wants the whole thing on its own servers.
3. **Bitbucket.** When your team already plans each task in Jira.

![A pull request flows from a feature branch toward a protected main branch drawn with a lock. On the way it must pass two gates: one review approved, and all tests passed. Beside the flow, an issue numbered 42 is linked, with the words Closes #42, and it closes when the merge lands. Below, three hosts that run this flow are named: GitHub, GitLab and Bitbucket.](https://learn.benibix.com/diagrams/dev3-git-hosting.svg)

### Example: A bug closes itself

Emma's shop has issue #42: the basket forgets items after 10 minutes. She fixes it on a branch and writes Closes #42 in the pull request.

When a teammate merges it into main, issue #42 closes by itself, with a link to the fix. Nobody has to remember to tidy the list.

**Words in this lesson:** [GitHub](https://learn.benibix.com/term/development/github), [GitLab](https://learn.benibix.com/term/development/gitlab), [Bitbucket](https://learn.benibix.com/term/development/bitbucket), [GitHub Issues](https://learn.benibix.com/term/development/github-issues), [Jira](https://learn.benibix.com/term/business/jira)

> **The one thing to remember.** Git saves the history and moves commits. The host adds the people part: pages, issues, reviews and tests.

**Question:** What is a merge request in GitLab?

**Answer:** The same thing GitHub calls a pull request. GitLab and GitHub use two names for one idea. It is a page that asks for a branch to be merged. It shows the changes and gives a place to review them.

---

Source: https://learn.benibix.com/learn/development-version-control/github-gitlab-and-bitbucket
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
