Git Commands Cheat Sheet for Beginners

Every developer needs this. Saving this = never Googling basic Git again. What is Git? A system that tracks every change in your code over time. Think of it as unlimited undo for your entire project. With collaboration built in. 4 things you need to understand first:   • Repository: Your project + its complete history   • Working Directory: What your code looks like right now   • Staging Area: Changes you're preparing to save   • Commit: A snapshot of your project at that moment The Git rules nobody tells juniors: 1. Commit small. Commit often. Don't let changes pile up. Smaller commits = easier to find what broke. 2. One change per commit. Future you will thank present you. So will your team. 3. Write real commit messages. "Fixed stuff" helps nobody. "Fixed null pointer in user auth flow" helps everyone. 4. Pull before you push. Always. Sync with your team before starting new work. Saves hours of conflict resolution. 5. Delete merged branches. Clean repo = clear mind. 6. Code reviews are not optional. They catch what you missed. Every time. 7. Resolve conflicts carefully. Don't just accept changes blindly. Test after every merge. Pro tip: Ditch the GUI. Use the command line. You'll understand Git 10x faster. The commit that ends every Friday: git commit -m "works on my machine" We've all been there. Save this. Your future self will thank you. What's your most used Git command? Drop it below.

You're Googling Git commands every single day. And it's killing your momentum. The Git commands I actually use daily: 1. Setup & Config git config --global user.name "Your Name" git config --global user.email "you@email.com" 2. Start Fresh git init → New repo git clone <url> → Copy existing repo 3. Daily Workflow git status → What changed? git add . → Stage everything git commit -m "message" → Lock it in git push → Send to remote git pull → Get latest changes 4. Branching (the lifesaver) git branch → List branches git branch <name> → Create branch git checkout <name> → Switch branch git checkout -b <name> → Create + 5. Switch git merge <branch> → Combine branches 6. Undo Mistakes git reset HEAD~1 → Undo last commit git checkout -- <file> → Discard changes git stash → Save work for later git stash pop → Bring it back 7. Check History git log → See commit history git diff → What changed? ⏩ The ones that saved me multiple times: git stash → When you need to switch tasks NOW git reset --soft HEAD~1 → Fix that bad commit message git checkout -b → Stop working on main by accident 📌 What I wish I knew earlier: You don't need to memorize 100 commands. Master these 15 and you're 90% there. Git isn't scary. It's just poorly explained. Learn the core workflow. Reference the rest when needed. 📄 Here is a complete Git cheatsheet with commands organized by use case... setup, daily workflow, branching, fixing mistakes, and advanced operations. Comment "GIT" and I'll send it over. 🔁 Repost if someone on your timeline needs to stop Googling Git commands ➕ Follow Arijit Ghosh for more #Git #GitHub #VersionControl #DevTools #Programming #Coding #SoftwareDevelopment #TechTips

My GIT - Cheat sheet 𝐏𝐫𝐨 𝐭𝐢𝐩 - To learn Git better, ditch the GUI and use the command line. 𝐖𝐡𝐚𝐭? A distributed version control system that tracks changes in files over time. 𝐖𝐡𝐲? Enables collaboration, branching, merging and a complete project history. 📌 𝐊𝐞𝐲 𝐓𝐞𝐫𝐦𝐢𝐧𝐨𝐥𝐨𝐠𝐢𝐞𝐬 - ◾ Repository A directory containing your project's complete history. ◾ Working Directory The current state of your project files. ◾ Staging Area (Index) Where you prepare changes for the next commit. ◾ Commit A snapshot of your project at a specific point in time. ◾ Branch A separate line of development. Remote: A version of your repository hosted on a server (e.g., GitHub, GitLab). 📌 𝐆𝐢𝐭 𝐁𝐞𝐬𝐭 𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐞𝐬 [1.] Commit Early, Commit Often ◾ Don't let changes pile up. ◾ Commit frequently to create smaller, more manageable snapshots of your work. ◾ This makes it easier to track progress, identify issues and revert if needed. [2.] One Change per Commit ◾ Keep your commits focused on a single logical change or feature. ◾ This improves readability and makes it easier to isolate and revert specific changes. [3.] Clear Commit Messages ◾ Write concise yet descriptive commit messages that explain what you changed and why. ◾ This makes it easier for you and your collaborators to understand the purpose of each commit in the future. ◾ Include some change or ticket # [4.] Merge or Rebase ◾ Use git merge to combine branches, or git rebase to apply your changes on top of another branch. ◾ Choose the method that best suits your workflow and preferences. [5.] Delete Merged Branches ◾ Once a branch has been merged, delete it to keep your repository tidy and avoid confusion. [6.] Pull Regularly ◾ Always fetch and merge the latest changes from the remote repository before starting new work. ◾ This helps avoid conflicts and keeps your local repository in sync with your team. [7.] Code Reviews ◾ Use pull requests or similar mechanisms to get feedback on your changes before merging them into the main branch. ◾ Code reviews help catch errors, improve code quality and ensure consistency across the codebase. [8.] Resolve Conflicts Carefully ◾ If conflicts arise when merging branches, resolve them carefully and thoroughly. ◾ Test your changes after resolving conflicts to ensure everything works as expected. git commit -m "works on my machine" 🙂 Follow Mayank for more such insights.

Imagine you are working on a feature on Git branch `feature1`. You have made good progress on this feature, with major changes across the project. As usual, in between, you got a “priority request” to verify an issue happening on `main` branch. Now, to verify the issue, you need to check out `main` branch. But you can’t unless you discard or stash your changes. This may break your current project setup and flow. Is it possible to switch to another branch without disturbing the current working branch and project setup? Yes, it's possible through **Git Worktree**. 👉 Details in my latest post: https://lnkd.in/gE-FkhQ7 #git

Git & GitHub Basics: The Foundation Every Developer Must Know: What is Git? 👉 Git is a distributed version control system that tracks changes in your code and helps manage project history. In simple words: Git remembers who changed what, when, and why in a project. What is GitHub? 👉 GitHub is a cloud-based platform that hosts Git repositories and enables collaboration. In simple words: GitHub is an online storage + collaboration platform for Git projects. 🌟 Importance of Using GitHub: 1️⃣ Version Control – Safely tracks and manages all code changes. 2️⃣ Collaboration – Allows multiple developers to work on the same project without conflict. 3️⃣ Backup & Security – Stores your code securely in the cloud. 4️⃣ CI/CD & Automation – Enables automated build, test, and deployment pipelines. 🔄 Git Lifecycle Workflow:     Working Directory (Edit / Create Files)            ↓  git add       Staging Area (git add .)             ↓  git commit -m "message"       Local Repository (git log)            ↓  git push origin main     Remote Repository (GitHub)            ↑  git pull            ↑  git fetch + git merge ⚡ Most Important Git Commands: git init        git status        git add filename    git add .        git commit -m "message"    git log            git diff        git reset filename    git clone repository_url   git remote add origin url   git push origin main    git pull origin main    git branch        git branch branch-name    git checkout branch-name git checkout -b branch-name git merge branch-name       git branch -d branch-name git stash           git stash pop           git rebase branch-name

𝑼𝒏𝒅𝒆𝒓 𝒕𝒉𝒆 𝑯𝒐𝒐𝒅: 𝑮𝒊𝒕 & 𝑩𝒊𝒕𝒃𝒖𝒄𝒌𝒆𝒕 — the clarity I wish I had earlier I spent almost 2 days trying to truly understand Git and Bitbucket. Not commands. Not diagrams. But what actually happens under the hood. Here’s the clarity that finally clicked — sharing it so someone else gets it in the first read. 🔹 1. 𝐓𝐡𝐞𝐫𝐞 𝐚𝐫𝐞 𝐓𝐖𝐎 𝐆𝐢𝐭 𝐫𝐞𝐩𝐨𝐬𝐢𝐭𝐨𝐫𝐢𝐞𝐬, 𝐧𝐨𝐭 𝐨𝐧𝐞 𝐋𝐨𝐜𝐚𝐥 𝐆𝐢𝐭 → on your laptop 𝐒𝐞𝐫𝐯𝐞𝐫-𝐬𝐢𝐝𝐞 𝐆𝐢𝐭 → on Bitbucket’s server 👉 Bitbucket does not replace Git 👉 Bitbucket wraps and exposes a server-side Git repository Git exists on both sides. 🔹 2. 𝐆𝐢𝐭 𝐢𝐬 𝐭𝐡𝐞 𝐞𝐧𝐠𝐢𝐧𝐞. 𝐁𝐢𝐭𝐛𝐮𝐜𝐤𝐞𝐭 𝐢𝐬 𝐭𝐡𝐞 𝐢𝐧𝐭𝐞𝐫𝐟𝐚𝐜𝐞. 𝐆𝐢𝐭 𝐢𝐬 𝐫𝐞𝐬𝐩𝐨𝐧𝐬𝐢𝐛𝐥𝐞 𝐟𝐨𝐫: tracking file changes creating commits managing branches merging code 𝐁𝐢𝐭𝐛𝐮𝐜𝐤𝐞𝐭 𝐩𝐫𝐨𝐯𝐢𝐝𝐞𝐬: UI permissions Pull Requests code review & approvals 👉 All real work is done by Git 👉 Bitbucket adds visibility and control 🔹 3. 𝐂𝐨𝐦𝐦𝐢𝐭 𝐡𝐚𝐩𝐩𝐞𝐧𝐬 𝐎𝐍𝐋𝐘 𝐢𝐧 𝐆𝐢𝐭 (𝐥𝐨𝐜𝐚𝐥𝐥𝐲) When you modify files → Git sees changes When you commit: Git saves a snapshot Git creates a commit ID This happens only in local Git Bitbucket has no role here 👉 Commits are Git objects, not Bitbucket actions 🔹 4. 𝐏𝐮𝐬𝐡 𝐜𝐨𝐩𝐢𝐞𝐬 𝐜𝐨𝐦𝐦𝐢𝐭𝐬 𝐭𝐨 𝐬𝐞𝐫𝐯𝐞𝐫-𝐬𝐢𝐝𝐞 𝐆𝐢𝐭 git push does NOT create new commits 𝐈𝐭 𝐜𝐨𝐩𝐢𝐞𝐬 𝐭𝐡𝐞 𝐬𝐚𝐦𝐞 𝐜𝐨𝐦𝐦𝐢𝐭𝐬: from local Git to server-side Git (on Bitbucket) 👉 After push: Server-side Git already has updated files Changes exist in the feature branch Bitbucket UI just shows what Git already has. 🔹 5. 𝐅𝐞𝐭𝐜𝐡 𝐯𝐬 𝐏𝐮𝐥𝐥 (𝐢𝐦𝐩𝐨𝐫𝐭𝐚𝐧𝐭 𝐝𝐢𝐬𝐭𝐢𝐧𝐜𝐭𝐢𝐨𝐧) 𝐅𝐞𝐭𝐜𝐡: Downloads information from server Git Does NOT change your files 𝐏𝐮𝐥𝐥: Fetch + merge Updates your local files 👉 Both are Git operations, not Bitbucket logic. 🔹 6. 𝐏𝐮𝐥𝐥 𝐑𝐞𝐪𝐮𝐞𝐬𝐭 𝐢𝐬 𝐍𝐎𝐓 𝐆𝐢𝐭 𝐏𝐮𝐥𝐥 𝐑𝐞𝐪𝐮𝐞𝐬𝐭 (𝐏𝐑): belongs to Bitbucket is for comparison, review, and approval 𝐏𝐑: does NOT create commits does NOT change code does NOT copy files 👉 PR is a decision layer, not an execution layer 🔹 7. 𝐌𝐞𝐫𝐠𝐞 𝐢𝐬 𝐰𝐡𝐞𝐫𝐞 𝐜𝐨𝐝𝐞 𝐚𝐜𝐭𝐮𝐚𝐥𝐥𝐲 𝐦𝐨𝐯𝐞𝐬 𝐛𝐫𝐚𝐧𝐜𝐡𝐞𝐬 When PR is approved and merged: Bitbucket UI triggers the action Git performs the merge Feature branch commits are applied to target branch (main/develop) 👉 Merge is Git’s job 👉 PR only controls when merge is allowed #git #bitbucket

🚀 Git & GitHub – Important Commands + Difference (Complete Guide) As a developer, version control is a must-know skill. Here are the most important Git commands + clear difference between Git & GitHub 👇 🔥 What is Git? Git is a distributed version control system used to track changes in source code during development. 🔥 What is GitHub? GitHub is a cloud-based platform that hosts Git repositories and enables collaboration. 👉 Simple Line: Git tracks code. GitHub stores code online. 💻 Most Important Git Commands (Practical Use) 1️⃣ Initialize Repository git init Creates a new Git repository. 2️⃣ Check Status git status Shows modified and untracked files. 3️⃣ Add Files to Staging git add . Moves files to staging area. 4️⃣ Commit Changes git commit -m "Your message" Saves snapshot of changes. 5️⃣ Connect to GitHub git remote add origin REPO_URL Links local repo to GitHub. 6️⃣ Push Code to GitHub git push -u origin main Uploads code to GitHub. 7️⃣ Pull Latest Changes git pull origin main Fetches and merges latest updates. 8️⃣ Clone Repository git clone REPO_URL Downloads repo from GitHub. 9️⃣ Branching git checkout -b feature 🔟Merge branch git merge feature 🎯 Basic Git Workflow Code → git add → git commit → git push 💡 Why Interviewers Ask This? Because Git shows: Collaboration skills Project handling ability Real-world development experience If you found this helpful, comment "GIT" and I’ll share advanced concepts like: Rebase vs Merge Cherry-pick Reset vs Revert Merge Conflicts Explained #VersionControl #Git #GitHub #Developers #Coding #Tech

🚀 Git Cheat Sheet – Every Developer Must Know! 💻✨ Whether you’re a beginner or brushing up your skills, these Git commands are 🔑 for daily development 👇 📁 Repository Setup 🆕 git init → Initialize a new Git repository 🌐 git clone <repo-url> → Clone an existing repository 📌 Basic Workflow 📄 git status → Check file status ➕ git add . → Stage all changes 📝 git commit -m "message" → Save changes locally 🌿 Branching 🌱 git branch → List branches 🔀 git checkout -b branch-name → Create & switch branch 🔁 git merge branch-name → Merge branch into current ⬆️⬇️ Remote Repository 🚀 git push origin branch-name → Push code to remote 📥 git pull → Fetch & merge latest changes 🔗 git remote -v → View remote URLs 🕵️ History & Logs 📜 git log → View commit history 🔍 git diff → See code differences ⚠️ Undo & Fix ♻️ git reset --hard HEAD → Reset changes ❌ git checkout -- file-name → Discard file changes 💡 Pro Tip: Mastering Git = Smooth teamwork + Safe code + Faster delivery 🚀 🔖 Save this post | ❤️ Like | 🔁 Share #Git #GitHub #Developer #Coding #FullStack #JavaDeveloper #WebDevelopment #LearnGit

💻 Git commands I’ve used 99% of the time in 3+ years... You don’t need to memorize 200 Git commands. You just need to master the ones that actually power your daily workflow. Here’s my real-world Git toolkit: 🔹 𝗗𝗮𝗶𝗹𝘆 𝗕𝗮𝘀𝗶𝗰𝘀 👉 git status – Check current changes 👉 git diff – See what changed 👉 git add <file> – Stage changes 👉 git commit -a -m "message" – Commit updates 👉 git log --stat – Review commit history 🔹 𝗕𝗿𝗮𝗻𝗰𝗵𝗶𝗻𝗴 & 𝗖𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗶𝗼𝗻 👉 git checkout -b <branch> – Create new branch 👉 git checkout <branch> – Switch branch 👉 git branch – List branches 👉 git merge – Merge branches 👉 git push origin <branch> – Push changes 👉 git pull – Sync latest changes 🔹 𝗙𝗶𝘅𝗶𝗻𝗴 𝗠𝗶𝘀𝘁𝗮𝗸𝗲𝘀 (𝗛𝗮𝗽𝗽𝗲𝗻𝘀 𝘁𝗼 𝗘𝘃𝗲𝗿𝘆𝗼𝗻𝗲 😅) 👉 git commit --amend – Edit last commit 👉 git reset HEAD~1 – Undo last commit (keep changes) 👉 git reset --hard – Reset completely (careful ⚠️) 👉 git revert – Safely undo via new commit 👉 git rebase -i – Clean up commit history 🔹 𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗯𝘂𝘁 𝗨𝘀𝗲𝗳𝘂𝗹 👉 git stash / git stash pop – Temporarily save changes 👉 git cherry-pick <commit> – Apply specific commit 👉 git show <commit> – Inspect commit details 👉 git branch -D <branch> – Delete branch 👉 git format-patch / git apply – Share patches 👉 git clone – Copy a repository That’s it. In reality, strong Git fundamentals > knowing every obscure command. Master these, and you’re already ahead of most developers. Follow Ritik Jain for more practical engineering tips 🚀 Image credit goes to respective owner... #Git #SoftwareEngineering #DeveloperTips #Programming #TechCareers #VersionControl #Coding

Git is not a version control system, it’s a lifestyle choice. Some daily Git “adventures”: - git status – The “what did I break this time?” command. - git pull – Merge conflicts as a service. - git push – Works perfectly… until it’s Friday 6 PM. - git log – Archaeology of bad commit messages: - “fix stuff” - “final fix” - “final_final_fix” - “please_work” Branch strategy in theory: main = stable develop = testing feature/* = focused work Branch strategy in reality: main main-final main-new main-new-final-2 Real Git challenges no one prepared us for: Solving merge conflicts written by someone who has left the company. Doing git rebase with confidence while your soul quietly leaves your body. Force-pushing to the wrong branch and then pretending “it was part of the plan.” And yet, for all the chaos, there’s nothing more satisfying than: Clean git status Green CI One meaningful commit message: “Refactored, tested, documented. Future me, you’re welcome.” #git #software #mern #javascript #codinghumour