Git Commands for Beginners: 20 Commands Explained in Plain English

Students starting web development often ask how many Git commands they need to learn before their first internship. Fewer than you'd think. The Git commands for beginners in this guide come to about 20, and you'll use six of them almost every day: status, add, commit, switch, pull and push.

The rest are for setup, branching and fixing mistakes. You'll learn them faster once the daily six feel automatic. In this guide you'll find:

• The real difference between Git and GitHub, in two short paragraphs
• A one-page glossary of commands with what each one does and when to type it
• Safe ways to undo a bad commit without losing your work
• A seven-day practice plan you can follow on any Windows laptop
• Why a tidy GitHub profile helps when you apply to software houses in Pakistan

Git and GitHub: What's the Difference?

Git is a free version control program that runs on your own computer. It records snapshots of your project folder, so you can see what changed, when and why. It works without internet, and it doesn't need an account.

GitHub is a website that stores copies of Git projects online. It adds things Git doesn't have: a web page for each project, pull requests for code review, issue tracking and free hosting for simple sites. Think of Git as the camera and GitHub as the shared album. GitLab and Bitbucket are other albums that work with the same camera.

This matters because many beginners install GitHub Desktop, click a few buttons and never learn what's happening underneath. That works until a merge goes wrong. Learning the commands first means you can fix problems in any tool, including the Git panel inside VS Code.

How Does Git Track Your Work?

Git keeps your work in three places. Once you see them, every command makes more sense.

The staging area confuses most people at first. Here's why it exists. Say you fixed a login bug and also changed the footer color. Those are two different ideas. With staging, you add only the login file, commit it with a clear message, then commit the footer separately. Your history now tells a clean story, which helps a lot when you need to find where a bug came from.

Before You Start: Install Git and Set Your Identity

On Windows, download Git for Windows from the official git-scm.com install page. When this guide was written, the page listed version 2.56.0(2), released on October 5, 2026. The default installer options are fine for beginners. It also installs Git Bash, a terminal where every command in this guide works exactly as shown.

Next, tell Git who you are. Every commit carries a name and email, so use the email linked to your GitHub account:

git config --global user.name "Your Name"
git config --global user.email [email protected]
git config --global init.defaultBranch main
git config --list

The third line needs a word of explanation. According to the Pro Git book's setup chapter, git init creates a branch called master by default, and Git 2.28 and later let you choose another name. GitHub names new branches main, so setting this once avoids a mismatch later. The last line prints your settings so you can check for typos.

Git Commands for Beginners: The Core Glossary

These 20 Git commands for beginners cover setup, saving, branching, syncing and undoing. Treat the table as your Git cheat sheet and keep it open in a browser tab for your first two weeks. You don't need to memorize it. After a few days of real use, most of it sticks on its own.

Starting and Saving Work, Step by Step

Most Git commands for beginners exist to support one loop, and you'll repeat it many times a day. Try it in an empty folder called practice:

1. Run git init once to start tracking the folder.
2. Create or edit a file, for example index.html.
3. Run git status. The file appears in red as untracked or modified.
4. Run git add index.html. Check git status again and the file turns green.
5. Run git commit -m "Add homepage layout".
6. Run git log --oneline to see your new commit at the top.

Write commit messages as short instructions in the present tense: "Fix mobile menu overlap", not "changes" or "final final 2". A reviewer at a software house will read your history, and vague messages make even good code look careless.

One more habit: add a file named .gitignore before your first commit. List folders like node_modules and files like .env in it. Git will then skip them, which keeps your repository small and keeps passwords and API keys off GitHub.

Branching Without Fear

A branch is a separate line of work. You can try an idea on a branch, and if it fails, main is untouched. The official git switch documentation describes git switch -c as creating a branch and then switching to it in one safe step. The older git checkout -b does the same job, and you'll still see it in many tutorials.

A realistic example: you're building a restaurant website for a client in Abbottabad and they ask for an online menu. You'd work like this:

git switch -c online-menu
# edit files, then add and commit as usual
git switch main
git merge online-menu

If Git reports a merge conflict, don't panic. It means both branches changed the same lines. Open the file, look for the <<<<<<< and >>>>>>> markers, keep the correct version, delete the markers, then add and commit. VS Code highlights conflicts and offers buttons to accept either side.

Working With GitHub: Clone, Push and Pull

To put a local project online, create an empty repository on GitHub without a README. Copy its URL, then run git remote add origin <url> followed by git push -u origin main. After that first push, plain git push is enough.

Guides on GitHub for beginners often skip this part. The first push is where many people get stuck, because GitHub rejects their account password. That's expected. GitHub's authentication docs say that on the command line over HTTPS you enter a personal access token where Git asks for a password, or you let a credential helper such as Git Credential Manager handle sign-in. Never paste a token into a file you commit, and treat it like a password.

On a shared project, start every session with git pull. If you skip it, your push may be rejected because GitHub has commits you don't. When that happens, pull, sort out any conflict, and push again. Never force-push to a shared main branch unless your team lead asks you to.

How Do You Undo a Mistake in Git?

Git is forgiving once you know which undo fits which situation. Use this as a quick guide:

• You edited a file and want the last committed version back: git restore index.html. Those edits are gone for good, so be sure.
• You staged the wrong file: git restore --staged config.js. The git restore documentation explains that --staged resets the staging area while leaving your working files alone.
• Your last commit message has a typo and you haven't pushed yet: git commit --amend -m "Correct message".
• A bad commit is already on GitHub: git revert <commit-id>. It adds a new commit that cancels the old one, so your teammates' history stays intact.

Be careful with git reset --hard, which you'll find in many forum answers. It discards uncommitted work with no warning. Run git status first, and if you're unsure, git stash your changes so you have a way back.

A Seven-Day Practice Plan

Reading a list of Git commands for beginners doesn't build the habit. Typing them does. Give it 30 to 45 minutes a day for one week:

1. Day 1: Install Git, set your name, email and default branch, and create a free GitHub account.
2. Day 2: In a practice folder, make five small commits. Read the log after each one.
3. Day 3: Use git diff and git restore on purpose. Break a file, then bring it back.
4. Day 4: Create two branches, change the same line in both, and merge them to cause a conflict. Resolve it.
5. Day 5: Push an existing project, such as a portfolio page, to GitHub and set up sign-in.
6. Day 6: Clone a repository, edit it on a laptop or a friend's machine, and practise pull and push.
7. Day 7: Write a README with screenshots and a live link. Pin the repository on your profile.

Is a GitHub Profile Worth Building in Pakistan?

For anyone aiming at web development work, yes. GitHub's Octoverse 2025 report says more than 180 million developers now use the platform. It adds that over 36 million joined in a single year and that nearly 1 billion commits were pushed in 2025. Git is the shared working language of that whole community.

For a fresh graduate, a GitHub link does practical work. A hiring manager at a software house in Islamabad, Lahore or Peshawar can open your projects, read your commit messages and judge your habits before you meet. A client on Upwork can do the same. Three well-documented projects with steady commits say more than a CV line that reads "familiar with Git."

If you're enrolled in a college, university or diploma program, check GitHub Education too. GitHub's student application page asks that you be at least 13 years old, enrolled in a degree- or diploma-granting program and able to show proof such as a dated student ID or enrollment letter. Approved students get the Student Developer Pack of free tools.

Once your projects are on GitHub, you can publish static ones for free. Our comparison of free web hosting for students covers GitHub Pages and the main alternatives. If you're still choosing what to build, the frontend developer roadmap for Pakistan suggests projects in a sensible order.

Practising Git Alongside PSTA's Full-Stack Course

PSTA's Full-Stack Web Development course runs for six months, uses AI tools throughout, and is built for beginners with no coding background. You move from HTML5 and CSS3 to modern JavaScript, React, Node.js with Express, MongoDB and MySQL, then PHP and WordPress for local client work. A module on AI for developers covers ChatGPT and GitHub Copilot, and the course ends with a capstone MERN application that you build and deploy live.

The current fee is Rs. 45,000 (regular Rs. 60,000), payable in two installments. You can join on campus at Mandian, Old College Road, opposite FIMS College, Abbottabad, join live online classes from any city, or combine the two. A new batch begins every month. Each project you build in the course is a natural repository for your GitHub profile, so the seven-day plan above fits well in your first weeks.

If you'd like a narrower start, look at the JavaScript programming course or the React.js course. The full list of programs sits on the courses page. When you're ready, the admission page explains how to enroll, and questions about class slots get answered on WhatsApp (+92 314 5424399).

Make Your First Commit Tonight

Pick one small thing you've already built, even a single HTML page. Install Git, run git init in that folder, and make one commit with a clear message. Then push it to a new GitHub repository. That one repository is the first entry in a portfolio that grows every time you code. Once these Git commands for beginners feel routine, learn pull requests next.