GitHub for Beginners: A Practical Step-by-Step Guide

July 07, 2026 Post a Comment

Hey there, friends! Welcome. If you have ever felt overwhelmed by the mere mention of terms like "repository," "commit," "push," or "pull request," you are in the right place. We have all been there. You start learning to code, or you join a new project team, and suddenly everyone is talking about Git Hub as if it is a second language. You see green contribution squares, complex terminal commands, and developers arguing over merge conflicts. It looks intimidating, but we promise you, it is not rocket science. Once you get the hang of the basic workflow, you will wonder how you ever lived without it.

In this guide, we are going to walk through Git Hub together, step-by-step. No jargon will be left unexplained, and we will build a solid foundation so you can confidently collaborate on projects, track your code history, and showcase your work to the world. Grab a cup of coffee, and let us dive in!

Understanding the Core: What is Git vs. Git Hub?

Before we press buttons and type commands, we need to clear up one of the biggest points of confusion for beginners: the difference between Git and Git Hub. They are related, but they are not the same thing.

Think of Git as the engine under the hood of your car. Git is a local version control system. It is a software tool that runs on your personal computer and tracks the changes you make to your files over time. Imagine you are writing a novel. Instead of saving files as "draft_v1.docx," "draft_v2_final.docx," and "draft_v3_really_final_this_time.docx," Git allows you to keep one single file and saves snapshots of your progress behind the scenes. You can travel back in time to any previous snapshot if you make a mistake.

Git Hub, on the other hand, is like the cloud-based garage where you park your car and show it off to others. It is a hosting service for Git repositories. It runs in the cloud and provides a beautiful web interface, project management tools, and social features. While Git manages your local changes, Git Hub lets you upload those changes to the internet so you can share them with team members, contribute to open-source software, or back up your work safely.

To summarize: Git is the tool you use locally; Git Hub is the platform where you store and share your Git projects globally. We need both to work effectively in modern software development.

Step 1: Setting Up Your Tools

First things first, we need to get our environment ready. We need to install Git on our local machine and create an account on Git Hub.

1. Create a Git Hub Account

Head over to github.com and sign up for a free account. Choose a username that you are comfortable sharing with potential employers, as your Git Hub profile will act as your digital portfolio.

2. Install Git on Your Computer

Depending on your operating system, the installation process varies slightly:

mac OS: Open your terminal and type git --version. If it is not installed, your system will prompt you to install Xcode Command Line Tools, which includes Git.

Windows: Go to git-scm.com and download the Git for Windows installer. Run the installer and accept the default settings (they are well-configured for beginners). This will also install "Git Bash," a terminal emulator that lets you run Git commands.

Linux: Open your terminal and run your package manager command. For Ubuntu/Debian, use sudo apt-get install git.

3. Configure Git

Once Git is installed, we need to tell it who you are. This information is attached to your commits so everyone knows who wrote the code. Open your terminal (or Git Bash on Windows) and run the following commands, replacing the placeholders with your actual details:

git config --global user.name "Your Name"

git config --global user.email "your.email@example.com"

Make sure the email address matches the one you used to register your Git Hub account.

Step 2: Creating Your First Repository

Now that our tools are ready, let us create our first repository (often shortened to "repo"). A repository is simply a folder where Git tracks your project files.

We will start by creating this repository on Git Hub first, then we will copy it down to our local computer.

1. Create the Repo on Git Hub

Log into your Git Hub account. In the top-right corner, click the "+" icon and select "New repository." Fill out the details as follows:

Repository name: Call it my-first-repo.

Description: Write a short description, like "Learning the basics of Git and Git Hub."

Public/Private: Choose "Public" so others can see your progress.

Initialize this repository with: Check the box that says "Add a README file." A README is a text file that explains what your project is about.

Click the green "Create repository" button at the bottom.

Congratulations! You have officially created your first remote repository. You should see your new repo page with the README.md file displayed.

Step 3: Cloning the Repository to Your Local Machine

Currently, your repository exists only on Git Hub's servers in the cloud. To actually write code, we need a copy of this folder on our local computer. The process of copying a remote repository to your computer is called cloning.

1. Copy the Clone URL

On your repository page on Git Hub, click the green "Code" button. Make sure the "HTTPS" tab is selected, and copy the URL provided (it will look like https://github.com/your-username/my-first-repo.git).

2. Run the Clone Command

Open your terminal (or Git Bash) and navigate to the directory where you want to store your project (for example, your Desktop or a dedicated projects folder). You can use the cd command to change directories:

cd Desktop

Now, run the clone command followed by the URL you copied:

git clone https://github.com/your-username/my-first-repo.git

Press Enter. Git will download the files from Git Hub and create a new folder named my-first-repo on your desktop. Navigate into this new folder:

cd my-first-repo

Step 4: The Classic Local Workflow (Add, Commit, Push)

This is where the magic happens. We are going to make changes to our files locally, save those changes in Git, and then upload them back to Git Hub. This cycle is the bread and butter of daily development.

1. Make a Change

Open your favorite text editor (like VS Code, Notepad, or Text Edit) and open the README.md file inside your my-first-repo folder. Let us add a new line of text to it:

# My First Repo Learning the basics of Git and Git Hub.

Today, I am learning how to use Git commands!

Save the file.

2. Check the Status

Go back to your terminal. We want to see what Git thinks about our changes. Run the following command:

git status

Git will respond by telling you that README.md has been modified. The file name will likely appear in red, indicating that the changes are unstaged.

3. Stage the Changes

Before we save our changes in Git's history, we must select which files we want to save. This is called "staging" your files. Think of it like packing items into a box before shipping it. To stage our modified README file, run:

git add README.md

If you have modified multiple files and want to stage all of them at once, you can run:

git add .

Run git status again. You will see that the file name has turned green. It is now staged and ready to be committed.

4. Commit the Changes

A "commit" is a permanent snapshot of your staged changes in your local Git history. Every commit needs a message that briefly explains what changes were made. Let us commit our changes with a clear message:

git commit -m "Update README with a learning update"

Your changes are now saved locally on your computer's Git database. However, they are still not visible on your Git Hub profile online.

5. Push to Git Hub

To send your local commits up to your remote repository on Git Hub, you need to "push" them. Run this command:

git push origin main

Note: Older repositories might use master instead of main as the default branch name. Since we created this repo fresh, it uses main.

If this is your first time pushing, Git might prompt you to log in or enter a Personal Access Token (PAT) for security. Follow the prompts to authenticate. Once complete, refresh your Git Hub repository page in your browser. You will see your updated README file online!

Step 5: Branching and Collaboration

When working on a team, you cannot have everyone pushing changes directly to the main codebase at the same time. That would cause chaos. Instead, we use branches.

Imagine the main branch as the trunk of a tree. It represents the working, production-ready version of your project. If you want to build a new feature or experiment, you create a branch off the trunk. You do your work on that branch, and when it is ready and tested, you merge it back into the main trunk.

1. Create and Switch to a New Branch

Let us create a new branch called feature-about-me. Run the following command:

git checkout -b feature-about-me

The -b flag tells Git to create a new branch, and checkout switches your active workspace to that branch. Any changes you make now will not affect the main branch.

2. Create a New File

Create a new file in your project folder named about.txt. Inside this file, write a sentence about yourself, like: "I am a future software engineer learning Git!" Save the file.

3. Stage, Commit, and Push the Branch

Let us run our standard workflow commands to save this new file and push the branch to Git Hub:

git add about.txt git commit -m "Add about.txt file"

git push origin feature-about-me

Because this branch only exists on your computer initially, we specify origin feature-about-me to tell Git Hub to create this new branch on the remote server too.

4. Open a Pull Request (PR)

Now, go to your repository page on Git Hub. You will see a yellow banner pop up saying "feature-about-me had recent pushes less than a minute ago." Click the green "Compare & pull request" button next to it.

A Pull Request is a formal request to merge your branch's changes into the main branch. It allows your teammates to review your code, leave comments, and suggest edits before the changes become official. Write a description of what you did and click "Create pull request."

5. Merge the Pull Request

Since you are the owner of this repository, you can merge it yourself. Scroll down on the PR page and click the green "Merge pull request" button, then click "Confirm merge."

Your changes from the feature-about-me branch are now officially part of your main branch! You can safely delete the branch on Git Hub using the button provided to keep things clean.

Key Points and Best Practices for Beginners

As you continue your coding journey, keeping these best practices in mind will save you from major headaches down the road:

Commit often, commit small: Do not wait until you have written 500 lines of code to make a commit. Make small, logical commits. It makes tracking down bugs much easier.

Write descriptive commit messages: "Fixed bug" or "changes" are not helpful. Use messages like "Fix navigation bar alignment on mobile" or "Add validation logic to login form."

Always pull before you push: If you are working with others, they might have pushed changes to Git Hub while you were working. Run git pull origin main to update your local machine with the latest changes before you try to push your own.

Use a .gitignore file: There are some files you never want to upload to Git Hub, such as API keys, configuration files containing passwords, or large system folders like node_modules. A .gitignore file tells Git to ignore these files completely.

Questions and Answers

Q1: What is the difference between Git and Git Hub?

Git is the command-line tool that runs locally on your computer to track changes in your code files. Git Hub is a cloud-based service that hosts Git repositories online, allowing developers to back up their projects, collaborate with teams, and manage workflows via a web interface.

Q2: How do I undo a commit I just made?

If you made a commit locally and realized you made a mistake before pushing it, you can undo it by running git reset --soft HEAD~1. This command removes the commit but keeps all your modified files staged in your workspace, allowing you to edit them and commit again.

Q3: What is a merge conflict and how do I fix it?

A merge conflict happens when two developers modify the same line of the same file on different branches, and Git does not know which version to keep. To fix it, open the affected file in your code editor. Git will highlight the conflicting lines. Decide which code to keep, delete the conflict markers (the arrows and equal signs), save the file, stage it, and commit the resolution.

Q4: Can I use Git Hub for non-coding projects?

Absolutely! Because Git tracks changes in text-based files, you can use Git Hub to write books, manage markdown-based note systems, collaborate on design documentation, or track configuration files. Any project that involves text files can benefit from version control.

Conclusion

And there you have it, friends! You have gone from understanding what version control is to creating a repository, cloning it, making changes, pushing updates, and merging your very first Pull Request. You now possess the fundamental skills that professional software developers use every single day.

Do not worry if you do not remember all the commands right away. Nobody does! Keep a cheat sheet handy, practice these steps on your own projects, and soon enough, Git and Git Hub will feel like second nature. Happy coding, and we will see you in the next guide!

TECH TUTORIAL