Git and GitHub for Beginners: A Simple Guide for Students

Have you ever saved files like project-final.zip, project-final-2.zip and project-final-REAL.zip? Every developer has. Git exists so that you never have to do that again.

Git and GitHub are two of the most useful tools you can learn as a student developer. Git keeps the full history of your code, so you can go back to any earlier version. GitHub stores that code online, so you can share it, work with a team and show your projects to companies. This guide explains both in simple words, with every command you need to get started.

💡 Quick answer: Git is a free tool on your computer that saves versions of your code, called commits. GitHub is a website that stores your Git projects online. The basic workflow is: make changes, git add them, git commit them with a message, and git push them to GitHub. Learn these, plus branches and pull requests, and you know enough Git for your first internship.

💡 Who is this guide for? Students and beginners who have never used Git, or who know a few commands but want to understand what they actually do.

In this guide:

1. What Is Git?
2. What Is GitHub?
3. Git vs GitHub
4. Why Every Student Developer Needs Git
5. How to Install and Set Up Git
6. The Basic Git Workflow
7. Your First Repository, Step by Step
8. Pushing Your Project to GitHub
9. Branches and Merging
10. Pull Requests: How Teams Work Together
11. The .gitignore File
12. Git Commands Cheat Sheet
13. How to Make Your GitHub Profile Stand Out
14. Common Beginner Mistakes and How to Fix Them

---

What Is Git?

Git is a version control system. It is a free program that runs on your computer and keeps track of every change you make to the files in a project.

Each time you reach a good point in your work, you save a snapshot called a commit. Every commit has a short message, like "Add login form", so you can later see what changed and when. If something breaks, you can go back to an earlier commit in seconds.

Git was created in 2005 by Linus Torvalds, the creator of Linux, and today almost every software team in the world uses it.

---

What Is GitHub?

GitHub is a website that hosts Git projects online. A project stored there is called a repository, or "repo" for short.

With GitHub you can:

• Back up your code online, so it is safe even if your laptop breaks
• Share your projects with anyone through a link
• Work on the same project with other developers
• Review each other's code through pull requests
• Host a simple website for free with GitHub Pages

GitHub is not the only option; GitLab and Bitbucket do similar jobs. But GitHub is the most popular, and it is where most recruiters look for your work.

---

Git vs GitHub

Many beginners think Git and GitHub are the same thing. They are not, but they work together.

A simple way to remember it: Git is like the camera that takes photos of your code, and GitHub is like the online album where you keep and share those photos.

---

Why Every Student Developer Needs Git

• You never lose work. Every commit is a save point you can return to.
• You can experiment safely. Try a new idea on a branch without breaking the working version.
• Teams depend on it. Every internship and job expects you to know the basics.
• Your GitHub is your portfolio. Recruiters often check it before reading your resume.
• It shows consistency. Regular commits show that you build things, not just study.

Learning Git is part of every developer path. It appears early in both our frontend developer roadmap and our Python developer roadmap, because you should use it from your very first project.

---

How to Install and Set Up Git

1. Download Git from the official Git website. On Windows, the installer also gives you "Git Bash", a terminal for Git commands. On a Mac, running git --version in the Terminal will offer to install it. On Linux, use your package manager, such as sudo apt install git.
2. Check that it worked by opening a terminal and typing git --version.
3. Tell Git who you are. This name and email appear on every commit you make:

bash
Copy
1git config --global user.name "Your Name"
2git config --global user.email "you@example.com"
3git config --global init.defaultBranch main

The last line names your first branch main, which is what GitHub uses too.

4. Create a free account on GitHub, using the same email address.

---

The Basic Git Workflow

Git moves your changes through three areas on your computer, and then to GitHub:

Figure 1: How a change travels from your editor to GitHub, and back with git pull.

Think of the staging area as a shopping cart. You pick the changes you want (git add), and then you check out with a message (git commit).

---

Your First Repository, Step by Step

Let's create a project and make your first commits. Open a terminal in an empty folder and run:

bash
Copy
1# 1. Create a new Git repository in this folder
2git init
3
4# 2. Create a file (or add your project files)
5echo "# My First Project" > README.md
6
7# 3. See what Git has noticed
8git status
9
10# 4. Stage the file
11git add README.md
12
13# 5. Save a snapshot with a message
14git commit -m "Add README"
15
16# 6. See your history
17git log --oneline

Now change something in README.md, run git add . (the dot means "everything that changed") and commit again. Run git log --oneline and you will see both commits, newest first.

💡 Pro Tip: Write commit messages that say what the commit does, like "Add contact form validation". Messages like "update" or "changes" don't help anyone, including you a month from now.

---

Pushing Your Project to GitHub

1. On GitHub, click New repository, give it a name (for example my-first-project) and click Create repository. Leave it empty, without a README, since you already have one.
2. Copy the repository's URL and connect your local project to it:

bash
Copy
1git remote add origin https://github.com/your-username/my-first-project.git
2git push -u origin main

The -u flag remembers the connection, so next time a plain git push is enough. The first time you push, Git asks you to log in. On Windows, Git opens your browser so you can sign in to GitHub; on other systems, GitHub's docs explain how to set up a token or SSH key.

To download an existing project from GitHub to your computer, use git clone with the repository's URL:

bash
Copy
1git clone https://github.com/your-username/my-first-project.git

---

Branches and Merging

A branch is a separate line of work. The main branch holds your working, stable code. When you build a new feature, you create a branch, work there, and merge it back into main when it is ready.

bash
Copy
1# Create a new branch and switch to it
2git switch -c add-navbar
3
4# ...edit files, then commit as usual...
5git add .
6git commit -m "Add responsive navbar"
7
8# Go back to main and merge the feature in
9git switch main
10git merge add-navbar

Figure 2: A feature branch splits off from main, gets its own commits and is merged back in.

Sometimes two branches change the same lines, and Git can't decide which version to keep. This is called a merge conflict. Git marks the conflicting lines in the file; you choose the right version, remove the markers, and commit. It looks scary the first time, but it is a normal part of teamwork.

---

Pull Requests: How Teams Work Together

In a team, you don't usually merge into main yourself. Instead, you push your branch to GitHub and open a pull request (PR). A pull request says: "Here are my changes; please review them before they go into main."

A typical team workflow looks like this:

1. Pull the latest main with git pull
2. Create a branch for your task
3. Commit your work in small, clear steps
4. Push the branch with git push -u origin your-branch-name
5. Open a pull request on GitHub with a short description and screenshots
6. A teammate reviews it and may suggest changes
7. Once it is approved, the branch is merged into main

This is exactly how most internships and companies work, so practising it on your own projects is a big advantage.

---

The .gitignore File

Some files should never go to GitHub: installed packages, build output and, most importantly, secrets such as passwords and API keys. A file named .gitignore in your project tells Git to ignore them.

text
Copy
1# Dependencies
2node_modules/
3venv/
4
5# Build output
6dist/
7.next/
8
9# Secrets and local settings
10.env
11.DS_Store

⚠️ Note: Add .gitignore before your first commit. If you accidentally push a password or API key, change that password or key straight away, because it stays in your Git history even after you delete the file.

---

Git Commands Cheat Sheet

The free Pro Git book and GitHub Docs explain every command in more depth.

---

How to Make Your GitHub Profile Stand Out

Your GitHub profile is often the first thing a recruiter sees, so a little effort here goes a long way.

• Add a profile README. Create a repository with the same name as your username, and its README appears on your profile. Write two lines about you, your skills and what you are learning.
• Pin your best 4–6 projects. Choose finished projects, not half-done practice folders.
• Write a README for every project: what it does, the tech stack, how to run it, a screenshot and a live link.
• Commit regularly. Small, steady commits show that you build things often.
• Use clear repository names, like weather-app-react, not project1 or test.

Figure 3: Four things that make your GitHub profile look professional.

Our guide to getting a web development internship with no experience explains how to use your GitHub and LinkedIn together when you apply.

---

Common Beginner Mistakes and How to Fix Them

Making mistakes in Git is completely normal. Almost everything can be undone, which is exactly why Git is so useful.

---

Final Thoughts

Git and GitHub feel strange for the first week and natural after a month. Start with add, commit and push on your own projects, then practise branches and pull requests. Keep your GitHub tidy, with clear READMEs and live links, and it becomes the strongest part of your portfolio.

The best way to get comfortable with Git is to use it on real projects with a team. You can do a free internship at MetaSkillGroup, where you build real features for our own products and our team reviews your work. Our online developer internship is open all year in six tracks. It takes about 2 minutes to apply, and your first exam attempt is free.