Author: Forrest Zhang

Recently, I noticed that many people do not fully understand GitHub, especially some less commonly used concepts such as fork, license, CLA, contributing, PR, and pull request. For people who are not professional software developers, GitHub can look confusing at first. There are many English terms, many buttons, and many workflows that seem technical. But the truth is simple: GitHub is mainly a platform for storing code, tracking changes, and letting people work together on software projects.

In this article, I will explain the most important GitHub concepts in plain English. The goal is not to turn you into an expert right away, but to help you understand what these words really mean and how they connect to each other in real projects.

What Is GitHub?

GitHub is a website and collaboration platform where developers store and manage software projects. You can think of it as a mix of a file storage system, a version history tool, and a teamwork platform. People use GitHub to keep code, documents, and project files in one place, and to track who changed what and when.

It is also important to know that Git and GitHub are not the same thing. Git is the version control system that records file changes. GitHub is the online platform that hosts Git-based projects and provides collaboration features such as issues, pull requests, and code reviews.

A simple way to remember it:

Git = the engine
GitHub = the website and collaboration space

What Is a Repository (Repo)?

A repository, usually called a repo, is the main container for a project on GitHub. It usually includes source code, configuration files, documentation, images, and version history. If someone says, “Here is the GitHub repo,” they simply mean, “Here is the project folder and its history on GitHub.”

A repo is the central place where a project lives. When people contribute to a project, open issues, or submit pull requests, they are usually doing it inside that repo.

What Is a Branch?

A branch is like a separate work line inside the same project. It lets people make changes without directly affecting the main version of the project.

For example, a project may have:

main — the main working version
feature/login-page — a branch for building a login page
bugfix/header-error — a branch for fixing a bug

This helps teams work safely. If a developer makes a mistake on a branch, it does not immediately break the main project.

What Is a Commit?

A commit is a saved change in the project history. Each commit records what was changed, who changed it, and usually includes a short message explaining the reason.

For example, a commit message might say:

Fix broken submit button on contact form

Over time, commits build a detailed timeline of the project. This is one of the biggest strengths of Git and GitHub. You can go back, compare versions, and understand how the project evolved.

What Is a Fork?

A fork means making your own copy of someone else’s repository under your own GitHub account. This is very common in open-source projects because you usually cannot directly edit the original project unless you are part of its core team.

So instead of changing the original repo directly, you:

Fork the repo to your own account
Make changes in your own copy
Ask the original project to review and accept your changes

Many beginners confuse fork with download, but they are not the same. A fork is an online copy on GitHub, not just a local copy on your computer.

What Is Clone?

Clone means copying a repository from GitHub to your local computer. After cloning, you can edit the files on your machine using tools like Visual Studio Code, IntelliJ, Eclipse, or any other editor.

So the difference is:

Fork = copy a repo to your own GitHub account
Clone = copy a repo from GitHub to your local computer

In many open-source workflows, people first fork a repo and then clone their fork to their computer.

What Is a Pull Request (PR)?

A pull request, often called a PR, is one of the most important concepts on GitHub. It is a request asking the maintainers of a project to review your changes and consider merging them into the main project.

In simple words, a pull request means:

“I made some changes. Please review them and decide whether they should become part of the project.”

Many people ask whether PR and pull request are different. They are not. PR is just the short form of pull request.

A pull request usually shows:

Which files were changed
What lines were added or removed
Comments from reviewers
Whether the changes are approved or need more work

What Is Merge?

Merge means combining changes from one branch into another branch, usually into the main branch. When a pull request is approved, the maintainers may merge it. That means the new changes officially become part of the project.

So the typical relationship is:

branch → commit → pull request → review → merge

What Is an Issue?

An issue is a discussion or tracking item in a repo. People use issues to report bugs, request new features, ask questions, or discuss project ideas.

In many open-source projects, maintainers prefer that contributors open an issue first before starting a large change. That avoids wasted effort and makes sure the idea matches the project’s direction.

What Is a License?

A license is the legal permission statement for a project. It tells others what they are allowed to do with the code.

A license may allow people to:

Use the code
Modify the code
Share the code
Use the code commercially

Some common licenses include MIT, GPL, and Apache 2.0. They are not the same. Some are more flexible, and some have stricter conditions.

One very important point is this: if a repository has no license, that does not mean it is free to use in any way you want. Many people get this wrong. Public code is not automatically open for unlimited use. If there is no license, you need to be careful.

What Is CONTRIBUTING?

CONTRIBUTING usually refers to a file called CONTRIBUTING.md in a GitHub repo. This file explains how people should contribute to the project.

It may include guidance such as:

How to report bugs
Whether to open an issue first
How to format commit messages
How to name branches
What coding style to follow
How to run tests before submitting changes

If a project has a clear CONTRIBUTING guide, that usually means it is more organized and more open to outside help.

What Is CLA?

CLA stands for Contributor License Agreement. This is a legal agreement that some projects ask contributors to accept before their code can be merged.

A CLA usually confirms that:

You have the right to submit the code
The code is your own work, or you are allowed to contribute it
The project can legally use your contribution

This is common in larger open-source projects, especially those backed by companies. It is mainly about legal clarity, not about coding skill.

What Is Code Review?

Code review is the process where other developers read and evaluate your changes before they are merged. They may point out bugs, unclear naming, missing tests, or design problems.

This is a normal and healthy part of software collaboration. It is not personal criticism. The goal is to improve quality and reduce mistakes.

What Does a Maintainer Do?

A maintainer is a person who helps manage and guide the project. Maintainers often decide which pull requests are accepted, which issues are important, and how the project should move forward.

Even in open-source projects, not everyone has equal authority. Usually, maintainers have the final decision on what becomes part of the official codebase.

What Is the Usual Open-Source Workflow?

If you want to contribute to an open-source project on GitHub, the common workflow looks like this:

Read the README to understand the project
Check the license
Read the CONTRIBUTING guide
Look at existing issues
Open an issue if needed
Fork the repo
Clone it to your computer
Create a new branch
Make your changes
Create commits
Push your changes to GitHub
Open a pull request
Respond to review comments
Wait for approval and merge

This may look like many steps, but after you do it once or twice, it becomes much easier.

Star, Watch, and Fork: A Quick Clarification

These three GitHub actions are often confused:

Star — similar to bookmarking or liking a repo
Watch — subscribe to notifications from the repo
Fork — create your own copy of the repo

They are completely different actions, so it is worth remembering the difference.

Why This Matters Even for Non-Developers

You do not need to be a full-time developer to benefit from understanding GitHub. Product managers, consultants, technical analysts, solution architects, and even curious learners can all gain value from knowing these concepts.

Today, many tools, frameworks, scripts, templates, and community solutions are shared through GitHub. If you understand the basic vocabulary, you can learn faster, communicate better with technical teams, and evaluate projects with more confidence.

Final Thoughts

GitHub may seem intimidating at first, but the core ideas are not that complicated. A repository stores a project, branches let people work safely, commits record changes, forks let you copy projects, and pull requests let you propose changes back to the original project. Licenses explain legal usage, CONTRIBUTING files explain participation rules, and CLAs handle contribution permissions.

Once you understand these basic terms, GitHub becomes much less mysterious. You do not need to master everything in one day. Just start by learning how to read a repo, understand the project structure, and recognize the main collaboration steps. That alone already puts you ahead of many people who use GitHub without really understanding it.

A Simple Guide to GitHub: Basic Concepts Many People Still Find Confusing