Recommended Free Tools
To start using GitHub, create a repository, make a branch, edit a file, commit your change, and open a pull request. You can learn that workflow entirely in a web browser: GitHub’s Hello World exercise requires an account, but no coding, command-line, or Git installation experience.
What GitHub does—and what you’ll do first
GitHub is a place to store project files and track changes to them. Its central workspace is a repository, often shortened to “repo.” Think of a repository as a project folder that also keeps a history of changes. In this first exercise, you will create a repository, work on a separate branch, edit a README file, save the edit as a commit, and propose it for review with a pull request.
The terms describe different parts of the workflow: a branch is where you work on a change, a commit records that change, and a pull request asks for the change to be reviewed and merged into another branch.
Choose a browser or local workflow
For a first lesson, the browser route has the fewest setup steps. GitHub’s Hello World tutorial walks through creating a repository and proposing a change without requiring you to install Git or use a command line.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Route | Where you work | What you need | Best suited to |
|---|---|---|---|
| GitHub in a browser | On GitHub.com | A GitHub account; no Git installation or command-line use for the Hello World exercise | Learning the basic repository, branch, commit, and pull request flow |
| GitHub Desktop | On your computer, with GitHub Desktop and an editor | GitHub Desktop, which includes Git, plus an editor of your choice | Working with local project files through a graphical interface |
| Git on the command line | On your computer using a terminal | A Git setup and a connection to GitHub using HTTPS or SSH | Learning to operate Git commands directly |
GitHub describes GitHub Desktop as a free, open-source graphical interface for common Git operations. Its first-repository guide covers signing in, creating or cloning a repository, making a branch, editing, committing, publishing, and opening a pull request. A separate local Git learning exercise lists Visual Studio Code as a prerequisite for that exercise; it is not a general requirement for using GitHub or completing the browser tutorial.
Create a repository and describe the project
Start with a small project, even if it contains only a few lines of text. In GitHub’s Hello World flow, create a new repository and give it a short, recognizable name. Add a description that tells visitors what the project is for. A README is a sensible starting file: it can explain the project, and GitHub Desktop’s repository guide notes that visitors see it when they learn about the repository.
Rank #2
Keep this first project simple. For example, a repository named my-first-project could have a README that says, “A place to practice using GitHub.” You do not need to write a program to learn the workflow.
Make a branch before changing a file
A branch is a separate version of the project where you can make a change without immediately changing the main branch. GitHub’s tutorial uses this separation so work can be proposed and reviewed before it is merged.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors- From the repository, open the branch selector.
- Enter a branch name that describes the task, such as
add-project-description. - Create the branch from the main branch.
Use a branch name that says what the change is about. The important habit is to make the change on your branch rather than directly on the main branch.
Edit a file and commit your change
Open the README on your new branch and make a small edit, such as adding one sentence about the project. The browser tutorial includes an in-browser file edit; for a local workflow, GitHub Desktop lets you open and edit files in an editor of your choice.
When the edit is ready, create a commit. A commit is a snapshot of the changes at that point in the project’s history. Give it a concise message that describes the action, such as “Add project description.” GitHub’s Getting started with Git guide demonstrates changing a README and committing the result.
Open a pull request to propose the change
A pull request is a proposal to review and merge changes from one branch into another. After committing, open a pull request from your working branch and select the main branch as the destination. Check that the change shown is the README edit you intended, then submit the pull request. GitHub’s Hello World exercise uses this step to propose the README change for merging into main.
In a shared project, reviewers can discuss the proposal before it is merged. In a practice repository, you can use the pull request to see how the review-and-merge process works.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Merge the change and start the next one
Once the pull request is ready, merge it into main. For your next change, switch back to main before creating another branch; this gives the new branch a starting point that includes the change you just merged.
When working with a local copy, check whether the remote repository has newer changes before continuing. GitHub’s Git guide covers fetching and pulling remote changes so your local work can catch up.
What to learn after your first change
Repeat the same cycle with another small edit: branch, edit, commit, pull request, and merge. Once those concepts feel familiar, try the local route if you want to work on files on your computer. GitHub’s account onboarding guide covers connecting to GitHub, including HTTPS and SSH options; GitHub Desktop is another local option when you prefer a graphical interface.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
