Starting with Git can feel confusing at first, but once you understand a few core commands, it becomes one of the most useful tools for managing code. This guide explains Git and GitHub in a simple way, with clear examples you can follow step by step.<\/p>\r\n
Git is a version control system. It helps you track changes in your code over time.<\/p>\r\n
You can use Git to:<\/p>\r\n
GitHub is a website where developers store and manage Git repositories online.<\/p>\r\n
Git does the tracking on your computer. GitHub gives you an online place to keep the project, share it, and collaborate with others.<\/p>\r\n
A repository, or repo, is your project folder that Git tracks.<\/p>\r\n
A commit is a saved snapshot of your changes.<\/p>\r\n
A branch is a separate line of work. You can build a feature in a branch without touching the main code.<\/p>\r\n
Clone means downloading a GitHub repository to your computer.<\/p>\r\n
Push means sending your local commits to GitHub.<\/p>\r\n
Pull means getting the latest updates from GitHub to your computer.<\/p>\r\n
Staging means preparing files before making a commit.<\/p>\r\n
When you work with files in Git, they usually appear in one of these states:<\/p>\r\n
First, install Git on your computer.<\/p>\r\n
After installing, open Command Prompt, PowerShell, or Git Bash and check the version:<\/p>\r\n
git --version<\/code><\/pre>\r\nIf Git is installed correctly, you will see the installed version.<\/p>\r\n
Step 2: Configure Git for the First Time<\/h2>\r\n
Before using Git, set your name and email. This information is attached to your commits.<\/p>\r\n
git config --global user.name \"RIZWAN AKHTAR\"\r\ngit config --global user.email \"rizikmw@gmail.com\"<\/code><\/pre>\r\nTo view your saved Git configuration:<\/p>\r\n
git config --list<\/code><\/pre>\r\nTip:<\/strong> Use the same email that you use on GitHub if you want your commits linked to your GitHub account.<\/p>\r\nStep 3: Clone a Repository from GitHub<\/h2>\r\n
If a project already exists on GitHub, you can download it to your local machine using git clone<\/strong>.<\/p>\r\ngit clone <repository-link><\/code><\/pre>\r\nExample:<\/p>\r\n
git clone https:\/\/github.com\/RizwanKMW\/reviewsfunda.git<\/code><\/pre>\r\nThis command creates a copy of the project on your computer.<\/p>\r\n
Step 4: Check Repository Status<\/h2>\r\n
You can check the current state of your project files with:<\/p>\r\n
git status<\/code><\/pre>\r\nThis command shows:<\/p>\r\n
\r\n- which files changed<\/li>\r\n
- which files are staged<\/li>\r\n
- which files are not being tracked yet<\/li>\r\n<\/ul>\r\n
Step 5: Add Files to Staging<\/h2>\r\n
Before saving changes in Git, you need to add them to the staging area.<\/p>\r\n
Add one specific file<\/h3>\r\ngit add index.html<\/code><\/pre>\r\nAdd all changed files<\/h3>\r\ngit add .<\/code><\/pre>\r\nExample:<\/strong> If you edited index.html<\/strong> and style.css<\/strong>, then git add .<\/strong> will stage both files.<\/p>\r\nStep 6: Commit Changes<\/h2>\r\n
After staging files, save them with a commit.<\/p>\r\n
git commit -m \"Add initial files\"<\/code><\/pre>\r\nA good commit message should clearly explain what changed.<\/p>\r\n
Examples of better commit messages:<\/p>\r\n
\r\n- Add login page<\/li>\r\n
- Fix contact form validation<\/li>\r\n
- Update homepage content<\/li>\r\n<\/ul>\r\n
Step 7: Push Code to GitHub<\/h2>\r\n
After committing locally, send your changes to GitHub using:<\/p>\r\n
git push origin main<\/code><\/pre>\r\nHere:<\/p>\r\n
\r\n- origin<\/strong> = remote repository name<\/li>\r\n
- main<\/strong> = branch name<\/li>\r\n<\/ul>\r\n
Creating a New Git Repository from Scratch<\/h2>\r\n
If your project is only on your computer and not yet connected to GitHub, follow these steps.<\/p>\r\n
1. Go to your project folder<\/h3>\r\n
Open terminal inside your project folder.<\/p>\r\n
2. Initialize Git<\/h3>\r\ngit init<\/code><\/pre>\r\nThis turns your folder into a Git repository.<\/p>\r\n
3. Add all files<\/h3>\r\ngit add .<\/code><\/pre>\r\n4. Make your first commit<\/h3>\r\ngit commit -m \"Add initial files\"<\/code><\/pre>\r\n5. Connect your local project to GitHub<\/h3>\r\ngit remote add origin <repository-link><\/code><\/pre>\r\nExample:<\/p>\r\n
git remote add origin https:\/\/github.com\/username\/projectname.git<\/code><\/pre>\r\n6. Check branch name<\/h3>\r\ngit branch<\/code><\/pre>\r\n7. Rename branch to main<\/h3>\r\ngit branch -M main<\/code><\/pre>\r\n8. Push code to GitHub<\/h3>\r\ngit push -u origin main<\/code><\/pre>\r\nNote:<\/strong> It is origin<\/strong>, not origan<\/strong>.<\/p>\r\nUnderstanding Branches<\/h2>\r\n
Branches let you work on features or fixes without affecting the main project immediately.<\/p>\r\n
For example, if you want to create a new feature, you can create a branch for it. Once the feature is ready, you can merge it into the main branch.<\/p>\r\n
See all branches<\/h3>\r\ngit branch<\/code><\/pre>\r\nSwitch to another branch<\/h3>\r\ngit checkout branch-name<\/code><\/pre>\r\nCreate and switch to a new branch<\/h3>\r\ngit checkout -b new-branch-name<\/code><\/pre>\r\nDelete a branch<\/h3>\r\ngit branch -d branch-name<\/code><\/pre>\r\nMerging Branches<\/h2>\r\n
After finishing work in a branch, you can merge it into your main branch.<\/p>\r\n
Compare differences before merge<\/h3>\r\ngit diff branch-name<\/code><\/pre>\r\nMerge a branch into your current branch<\/h3>\r\ngit merge branch-name<\/code><\/pre>\r\nExample workflow:<\/strong><\/p>\r\n\r\n- Create branch login-page<\/strong><\/li>\r\n
- Work on login feature<\/li>\r\n
- Commit changes<\/li>\r\n
- Switch to main<\/strong><\/li>\r\n
- Run git merge login-page<\/strong><\/li>\r\n<\/ol>\r\n
Pull Latest Changes from GitHub<\/h2>\r\n
If another developer updated the project, or if you updated code directly on GitHub, you should pull the latest changes.<\/p>\r\n
git pull origin main<\/code><\/pre>\r\nThis downloads and merges the latest changes from GitHub into your local branch.<\/p>\r\n
Delete Files or Folders in Git<\/h2>\r\n
If you want to remove a file or folder from the repository, use:<\/p>\r\n
git rm file.txt\r\ngit rm -r folder-name<\/code><\/pre>\r\nThen commit and push:<\/p>\r\n
git commit -m \"Remove unused files\"\r\ngit push origin main<\/code><\/pre>\r\nUndoing Changes<\/h2>\r\n
Beginners often make mistakes. That is normal. These commands help you undo common changes.<\/p>\r\n
Discard changes in a file before staging<\/h3>\r\ngit checkout -- index.html<\/code><\/pre>\r\nThis restores the file to the last committed version.<\/p>\r\n
Unstage a file after git add<\/h3>\r\ngit reset index.html<\/code><\/pre>\r\nUndo last commit but keep changes<\/h3>\r\ngit reset --soft HEAD~1<\/code><\/pre>\r\nUndo last commit and remove changes<\/h3>\r\ngit reset --hard HEAD~1<\/code><\/pre>\r\nWarning:<\/strong> The hard reset command permanently removes changes that are not saved elsewhere.<\/p>\r\nHelpful Daily Git Workflow<\/h2>\r\n
Here is a simple daily routine for beginners:<\/p>\r\n
\r\n- Open project folder<\/li>\r\n
- Run git pull origin main<\/strong><\/li>\r\n
- Make your code changes<\/li>\r\n
- Run git status<\/strong><\/li>\r\n
- Run git add .<\/strong><\/li>\r\n
- Run git commit -m \"your message\"<\/strong><\/li>\r\n
- Run git push origin main<\/strong><\/li>\r\n<\/ol>\r\n
Example Full Workflow<\/h2>\r\n
Here is a complete beginner example from start to finish:<\/p>\r\n
git clone https:\/\/github.com\/username\/projectname.git\r\ncd projectname\r\ngit status\r\ngit add .\r\ngit commit -m \"Update homepage content\"\r\ngit push origin main<\/code><\/pre>\r\nHow to Create a README.md File<\/h2>\r\n
A README.md file explains your project. It is usually the first file people read on GitHub.<\/p>\r\n
Basic example:<\/p>\r\n
# Project Name\r\n\r\n## Description\r\nShort details about the project.\r\n\r\n## Features\r\n- Login system\r\n- Dashboard\r\n- Contact form\r\n\r\n## Installation\r\n1. Clone the repository\r\n2. Open the project\r\n3. Run the project\r\n\r\n## Author\r\nYour name<\/code><\/pre>\r\nBest Tips for Beginners<\/h2>\r\n\r\n- run git status<\/strong> often<\/li>\r\n
- write clear commit messages<\/li>\r\n
- pull latest changes before starting work<\/li>\r\n
- use branches for new features<\/li>\r\n
- do not use git reset --hard<\/strong> unless you are sure<\/li>\r\n
- practice with a test repository first<\/li>\r\n<\/ul>\r\n
Common Mistakes Beginners Make<\/h2>\r\n\r\n- forgetting to run git add<\/strong> before commit<\/li>\r\n
- pushing to the wrong branch<\/li>\r\n
- editing code without pulling latest updates<\/li>\r\n
- using unclear commit messages like update files<\/strong><\/li>\r\n
- confusing Git with GitHub<\/li>\r\n<\/ul>\r\n
Quick Command Summary<\/h2>\r\ngit --version\r\ngit config --global user.name \"Your Name\"\r\ngit config --global user.email \"youremail@example.com\"\r\ngit config --list\r\n\r\ngit clone <repository-link>\r\ngit status\r\ngit add .\r\ngit add index.html\r\ngit commit -m \"Your message\"\r\ngit push origin main\r\ngit pull origin main\r\n\r\ngit init\r\ngit remote add origin <repository-link>\r\ngit branch\r\ngit branch -M main\r\ngit checkout branch-name\r\ngit checkout -b new-branch-name\r\ngit branch -d branch-name\r\ngit diff branch-name\r\ngit merge branch-name\r\n\r\ngit rm file.txt\r\ngit rm -r folder-name\r\n\r\ngit reset index.html\r\ngit reset --soft HEAD~1\r\ngit reset --hard HEAD~1
xd
<\/code><\/pre>\r\nHow to clone private repositories to remote servers ie Github -> namecheap<\/strong><\/p>\r\n1. In namecheap generate keys using below command<\/strong><\/p>\r\nssh-keygen -t ed25519 -C \"server-deploy\"<\/code><\/pre>\r\nThis creates two files: ~\/.ssh\/id_ed25519 , ~\/.ssh\/id_ed25519.pub<\/p>\r\n
2. Copy the public key<\/strong>
cat ~\/.ssh\/id_ed25519.pub<\/p>\r\n3.Goto below directory and paste the public keys there<\/strong>
GitHub → Settings → SSH and GPG Keys → New SSH Key<\/p>\r\n4. Goto namecheap terminal and paste below command<\/strong><\/p>\r\ngit clone git@github.com:USERNAME\/REPOSITORY.git #this will clone zip source code<\/code><\/pre>\r\nto clone direct files use below commands<\/p>\r\n
cd ~\/public_html\r\ngit init\r\ngit remote add origin git@github.com:USERNAME\/REPOSITORY.git\r\ngit pull origin main<\/code><\/pre>\r\n <\/p>\r\n
5. Deploy updates from GitHub<\/strong><\/p>\r\ngit pull origin main<\/code><\/pre>\r\nDOWNLOAD LATEST CODE FROM GITHUB TO LOCAL<\/h2>\r\ngit fetch origin\r\ngit reset --hard origin\/main<\/code><\/pre>\r\nFinal Words<\/h2>\r\n
Git and GitHub may look technical in the beginning, but the basics are actually simple once you practice them. Start with cloning, checking status, adding files, committing, pulling, and pushing. After that, learn branches and merging. With regular use, these commands will become part of your normal coding workflow.<\/p>","category_id":"18","is_private":"0","created_at":"2023-04-14T02:27:37.000000Z","updated_at":"2026-04-04T00:44:32.000000Z","category":{"id":18,"user_id":"1","name":"Tutorials","slug":"tutorials-n3lw","parent_id":null,"created_at":"2023-04-01T17:24:32.000000Z","updated_at":"2023-04-01T17:24:32.000000Z"},"user":{"id":1,"name":"R GONDAL","email":"rizikmw@gmail.com","email_verified_at":null,"two_factor_confirmed_at":null,"current_team_id":"1","profile_photo_path":null,"created_at":"2023-03-12T10:49:33.000000Z","updated_at":"2025-01-10T12:59:00.000000Z","profile_photo_url":"https:\/\/ui-avatars.com\/api\/?name=R+G&color=7F9CF5&background=EBF4FF"}},"pageDesc":"Git and GitHub Tutorial for Beginners Starting with Git can feel confusing at first, but once you understand a few core commands, it becomes - Basic GitHub tutorial for developers (Updated: April 4, 2026) - Read more about Basic GitHub tutorial for developers at my programming site [SITE]","categories":[]}