How to Use GitHub (A Beginner's Guide to the Basics)

GitHub sounds like it's only for programmers, but the core idea is simple: it's a place to store a project, keep every version of it and let several people suggest changes without wrecking the original. Writers, designers and marketers use it too. Here are the five words you need, then the beginner workflow GitHub itself recommends, and the habits that stop you getting lost.

The five words to learn first

Word	Meaning
Repository	A project folder holding files, images and other folders
Branch	A separate version of the project you can change safely
Commit	A saved change with a message explaining why
Pull request	A proposal to merge your branch into another, for review
Merge	Combining the changes from one branch into another

GitHub's own Hello World tutorial teaches exactly these: repositories, branches, commits and pull requests. And it says you don't need to know how to code, use the command line or install Git to follow it. You just need a GitHub account.

Step 1: Create a repository

1. Select the plus icon in the upper-right corner of any page and click New repository.
2. Type a short, memorable name, such as hello-world.
3. Optionally add a description.
4. Choose whether the repository is Public or Private.
5. Tick Add a README file.
6. Click Create repository.

GitHub describes a repository as a folder for items that belong to the same project. The README file, written in Markdown, is where you explain what the project is. GitHub shows its contents on the front page of the repository, so it works like a shop window.

Step 2: Create a branch

Every repository starts with one branch called main, which GitHub treats as the definitive version. A branch is a safe copy for experimenting. Work on a branch doesn't appear on main until you merge it.

1. Click the Code tab of your repository.
2. Click the dropdown that says main.
3. Type a new branch name, such as readme-edits.
4. Click Create branch.

Step 3: Make and commit a change

1. On your new branch, click the README.md file.
2. Click the pencil icon to edit it and write a little about yourself.
3. Click Commit changes.
4. Write a commit message that explains what you changed and why.
5. Click Commit changes again.

A commit is a snapshot of your project at a point in time, and the message is for the next person (often you). Write 'Add contact details to README', not 'stuff'.

Step 4: Open a pull request

1. Click the Pull requests tab, then New pull request.
2. Choose your branch to compare against main.
3. Review the differences. Changes, additions and removals are shown in different colours.
4. Click Create pull request, give it a title and short description, and click Create pull request again.

The pull request is where collaboration happens. GitHub says you can open one as soon as you've made a commit and start a discussion, even before the work is finished. Reviewers can comment or propose changes before anything is merged.

Step 5: Merge it

When you're happy with the changes, merge the pull request so your branch's changes become part of main. In the tutorial you do this on your own repository, which makes it a safe place to practise the whole GitHub flow before you work on a bigger project.

A faster route: the quickstart

GitHub's quickstart for repositories promises you can create a repository and commit your first change in about five minutes. If you use the GitHub CLI, gh repo create does the first step from the command line. You can skip the prompts by giving the repository name and a visibility flag, such as --public or --private, and add --clone to copy it to your computer.

Habits that keep you out of trouble

• Make small commits with clear messages.
• Never work directly on main when others depend on it. Use a branch.
• Write a useful README on day one.
• Choose Private for anything you wouldn't put on a public noticeboard.
• Don't store passwords or keys in a repository.

Who benefits beyond developers

Anyone who works on documents with other people can use branches and pull requests for review: a policy document, a website's text, a set of templates. Because every change is recorded, you can always see who changed what and go back. If you're comparing tools, my guides to productivity tools for developers and top programming languages cover what else is out there.

What GitHub is not

GitHub isn't the same thing as Git, which is the version control software it's built on. Git tracks changes. GitHub is a website that hosts your Git projects and adds collaboration features such as pull requests and discussion. You can use GitHub entirely in your browser, as the Hello World tutorial does, without installing Git on your computer at all. Later, if you want to work on files locally, you can install Git or GitHub Desktop and sync your changes back.

Public or private?

When you create a repository you choose Public or Private. Public repositories can be seen by anyone, which suits open projects and portfolios. Private ones are limited to people you invite. If you aren't sure, choose private; you can usually make something public later, but you can't take back something that's been seen. Never put passwords, API keys or customer information in either kind.

My verdict

Do the Hello World tutorial once, in your own repository, and the vocabulary will stick. Learn to branch, commit and open a pull request, keep commit messages meaningful and keep sensitive data out of every repository.

Frequently asked questions

How do I use GitHub for beginners?

Create an account, make a repository, create a branch, edit a file and commit the change, then open and merge a pull request.

Do I need to know how to code to use GitHub?

No. GitHub's Hello World tutorial says you don't need to know how to code, use the command line or install Git.

What is a repository?

A repository is like a folder that holds the files and other items for a project.

What is a pull request?

A proposal to merge your changes into another branch, which lets others review and discuss them first.

What is the main branch?

By default every repository has a branch named main, which is considered the definitive branch.