Boost Dev Productivity with Git Worktrees

⚠️ I thought I just deleted hours of work. Turns out… Git saved me. I had just committed some code, but commit message wasn’t right. Usually, my flow is: git stash git reset --soft HEAD~1 git stash apply Recommit with a better message But this time, I skipped the stash step and ran git reset --hard HEAD~1 And immediately realised — the commit wasn’t pushed, and I hadn’t stashed anything. 😅 That’s when the panic started. Then I remembered: Git almost never truly deletes things immediately. I ran: git reflog And there it was — the “lost” commit. I restored it with: git reset --hard <commit-hash> Crisis avoided. 📚 But the bigger lesson wasn’t recovery, it was understanding Git more deeply. After restoring the commit, I also learned how to properly edit history: git commit --amend → modify the last commit message No stashing. No resetting. No unnecessary risk. 🛠️  Sometimes growth as a developer isn’t about writing more code. It’s about understanding the tools better #developers #git #versioncontrol #webdevelopment #shopifydeveloper #learninginpublic

🧠 Git Stash: The lifesaver every developer underuses Ever been in this situation? ❌ You’re mid-feature ❌ Your code is half-baked ❌ Suddenly… urgent bug fix request 🚨 That’s where git stash quietly saves your day. What git stash actually does It temporarily stores your uncommitted changes and gives you a clean working directory — without losing anything. Real-world use case You’re building Feature A 👉 Bug appears in production 👉 You don’t want to commit broken code git stash git checkout main # fix the bug git stash pop Boom 💥 — you’re back exactly where you left off. Pro tips most devs don’t know ✨ git stash -u → stash untracked files ✨ git stash list → see all stashes ✨ git stash apply stash@{1} → apply specific stash ✨ git stash drop → clean old junk Why this matters • Cleaner commits • Faster context switching • Less panic, more control If you’re not using git stash daily, you’re working harder than you need to. 💬 How often do you use git stash — daily, weekly, or only in emergencies? #Git #SoftwareDevelopment #DeveloperTools

Quick Git pro tip that saves hours during code reviews and keeps history readable: Use git rebase -i HEAD~n (interactive rebase) to squash, reorder, edit, or fixup commits before pushing. Example workflow: 1. git rebase -i HEAD~5 → opens editor with last 5 commits 2. Change “pick” to: • squash/s = combine into previous • fixup/f = combine but discard message • edit/e = pause to amend • reword/r = change commit message 3. Save & exit → Git applies changes step-by-step Pro moves: • Add exec lines to run tests mid-rebase • Use drop to remove bad commits entirely Clean history = happier teammates + easier bisects. Which rebase command do you use most often — squash, fixup, or something else? Share your favorite below 👇 #Git #DeveloperTips #CleanCode

💻 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 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. Image credit goes to respective owner... hashtag #Git hashtag #SoftwareEngineering hashtag #DeveloperTips hashtag #Programming hashtag #TechCareers hashtag #VersionControl hashtag #Coding

I used to avoid Git branches because I was scared of breaking everything 😅 One wrong command… and I thought my project was gone. But when I understood .gitignore, branch, and merge, Git started to feel safe , not scary. Here’s what changed for me:  .gitignore: Keep your project clean Not every file should be saved in Git. Some files are: Secret files (.env) Large folders (node_modules/) Log files (*.log) Create a file called: .gitignore These don’t belong in your repository. A simple .gitignore file keeps your project clean and protects sensitive data. Branch : Work without fear git checkout -b feature-name A branch is your safe space. You can test ideas, build features, fix bugs without touching your main project. Main stays stable. You experiment freely. Merge : Bring it back git checkout main git merge feature-name When your work is ready, merge it back. If you see a conflict, don’t panic. Fix it, save, commit and move on. The biggest lesson I learned? Git is not about being perfect. It’s about working without fear. If you're learning Git, what confused you most at the beginning? #Git #VersionControl #GitHub #Developers #CodingJourney #TechLearning

Imagine you’re working on some code and suddenly need to switch branches. Your work is not finished yet, so you don’t want to commit it. That’s where git stash helps. git stash temporarily saves your uncommitted changes and gives you a clean workspace. Think of it like keeping your work in a drawer and closing it for later. Basic Commands # Save your current work git stash # See all saved work git stash list # Want to commit all the saved changes git stash apply # Saves untracked files git stash -u # Saves ignore files,folder etc git status -a When should beginners use git stash? • When you need to switch branches quickly • When your work is half done • When you want to keep commit history clean • When you don’t want to lose changes git stash is safe, simple, and very useful once you start using Git daily #Git #BeginnerFriendly #VersionControl #LearningInPublic

Yesterday I learned something small in Git, but it actually made things clearer for me. I was working on my local branch and wanted to switch to a branch my teammate pushed. So I typed: git checkout friend-branch Git replied with: "pathspec did not match any file(s) known to git" For a second I thought I messed something up. After checking, I realized the branch was not local. It only existed on origin. That is when I discovered something I had never paid attention to before. The difference between git checkout and git switch. When I ran: git switch friend-branch Git automatically created a local tracking branch from origin and switched to it. It is a small thing. But moments like this remind me that being a developer is not just about learning new frameworks. It is about understanding your tools better every day. Every small mistake teaches something. Still learning. Always will. #Git #SoftwareDevelopment #LearningInPublic

Git is an essential skill for anyone starting their career in software or working in the tech industry. In this blog post, I break down the basics of Git using real-world examples to make it easy to understand and relatable. Feel free to share this with anyone who might need a straightforward introduction to Git.

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