Git Branching & GitHub Essentials for DevOps

🚀 Day 23 – Git Branching & My First Push to GitHub Today I unlocked one of the most powerful concepts in Git: 👉 Branching Yesterday I learned how to commit. Today I learned how real developers actually work. 🌿 What I Practiced Today ✅ Created and switched between multiple branches ✅ Understood how HEAD works ✅ Used git switch (modern way) instead of checkout ✅ Made feature-specific commits ✅ Verified branch isolation ✅ Deleted unused branches ✅ Pushed both main and feature-1 to GitHub ✅ Pulled changes made directly from GitHub And yes… My repo is now live on GitHub 🔥 🧠 Key Realizations 🔹 A branch is just a pointer to a commit — but it changes everything. 🔹 main should stay stable. Features belong in separate branches. 🔹 git pull = git fetch + git merge 🔹 origin is my remote repo. 🔹 upstream is the original repo (used in fork workflows). Switching branches literally feels like time travel ⏳ Your files change to match that branch’s history. 🌎 First GitHub Workflow Experience Local repo → Create branch → Commit → Push → View branches on GitHub → Pull changes This is how collaboration actually works in DevOps teams. 💡 Biggest Learning Git isn’t just version control. It’s: ✔ Controlled experimentation ✔ Safe collaboration ✔ Structured development ✔ Production protection Today I moved from “using Git” to “understanding Git.” Small steps. Strong foundations. 💪 Tomorrow — merging & real-world workflow. #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #Git #GitHub #VersionControl #DevOpsJourney

🚀 Day 58 – Wrapping Up Remaining Git Concepts 🚀 Today I completed the remaining Git topics, bringing together everything I’ve learned about version control and collaborative development. This phase helped reinforce how Git manages code history, teamwork, and project evolution efficiently 💻⚙️ 🔹 What I Focused On Today ✔ Git Tags Learned how to create tags to mark important points in the project history, such as releases or stable versions. ✔ Git Log & History Tracking Explored ways to view commit history clearly and understand how projects evolve over time. ✔ Ignoring Files with .gitignore Understood how to prevent unnecessary files (logs, node_modules, build files) from being tracked by Git. ✔ Remote Repository Management Revisited commands used to connect local repositories with remote ones and manage project synchronization. ✔ Best Practices for Git Workflow Focused on maintaining clean commits, proper branch usage, and organized repositories for professional development. 🔹 Reflection Completing Git feels like gaining a developer superpower ⚡ From basic commits to branching, merging, rebasing, and collaboration workflows — version control now feels much clearer and more structured. This knowledge will play a crucial role in team projects, open-source contributions, and professional development workflows. #Git #GitHub #VersionControl #DeveloperTools #FullStackJourney #100DaysOfCode #LearningEveryday #TechGrowth #SoftwareDevelopment 🚀

📌 Git & GitHub — Understanding Version Control the Simple Way Managing files manually often turns into something like this: project.txt project_final.txt project_final_v2.txt project_final_FINAL.txt Confusing, right? This is exactly the problem Git solves. Git works like a time machine for your work. Every change is tracked through commits, allowing you to move back to any version whenever needed. Instead of creating endless file copies, everything is organized inside a repository with a clear history. And when Git connects with GitHub, collaboration becomes powerful. Here are some core concepts that make Git & GitHub essential for developers: 🔹 Repositories – Project folders with version control 🔹 Commits – Save points that record changes 🔹 Branches – Parallel environments to experiment safely 🔹 Merging – Combining different development paths 🔹 Pull Requests – Suggesting and reviewing changes in teams 🔹 Issues & Discussions – Managing tasks and collaboration 🔹 GitHub Pages – Hosting project websites directly from a repository Version control is not just about code. It is about organization, collaboration, and confidence while building projects. Whether working solo or with teams, Git & GitHub make it possible to track progress, experiment safely, and contribute to open-source communities. #Git #GitHub #VersionControl #SoftwareDevelopment #DeveloperTools #OpenSource #TechLearning #Coding #DevCommunity #LearnInPublic

How Git Actually Works (Simple Explanation) Many developers use Git daily. But not everyone clearly understands what happens behind the scenes. Here’s the simple flow 👇 🖥️ 𝟭. 𝗪𝗼𝗿𝗸𝘀𝗽𝗮𝗰𝗲 This is where you write and edit your code. Files are modified here. When you run: git add You move changes to the next stage. 📦 𝟮. 𝗦𝘁𝗮𝗴𝗶𝗻𝗴 𝗔𝗿𝗲𝗮 This is like a preparation zone. You choose what changes will go into the next commit. When you run: git commit Changes move into your local repository. 💾 𝟯. 𝗟𝗼𝗰𝗮𝗹 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆 This is your local Git history. Commits are stored here on your system. To share changes: git push → sends code to remote. To get updates: git fetch → downloads changes git pull → fetch + merge together ☁️ 𝟰. 𝗥𝗲𝗺𝗼𝘁𝗲 𝗥𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝘆 This is GitHub, GitLab, or Bitbucket. It stores code online for collaboration. 💡 Simple Way to Remember: Workspace → Stage → Commit → Push Git isn’t complicated. It’s just a structured way to track and share changes safely. Once you understand this flow, Git becomes much easier. 🔖 Hashtags (SEO-friendly) #Git #VersionControl #GitHub #SoftwareDevelopment #WebDevelopment #DeveloperTips #ProgrammingBasics

𝗗𝗮𝘆 𝟮 – 𝗚𝗶𝘁 𝗖𝗼𝗺𝗺𝗶𝘁𝘀, 𝗥𝗲𝘀𝗲𝘁 & 𝗥𝗲𝗺𝗼𝘁𝗲 𝗢𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻𝘀 🔧 Continuing my Git & GitHub learning journey, today I practiced how developers save changes, undo mistakes, and interact with remote repositories. Understanding these commands is essential for managing real-world code changes. 🔹 𝗖𝗼𝗺𝗺𝗮𝗻𝗱𝘀 𝗜 𝗣𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝗱    ✨ 𝗧𝗿𝗮𝗰𝗸𝗶𝗻𝗴 𝗮𝗻𝗱 𝗰𝗼𝗺𝗺𝗶𝘁𝘁𝗶𝗻𝗴 𝗰𝗵𝗮𝗻𝗴𝗲𝘀    -> git status – Check current repository status    -> git add <file> – Stage changes for commit    -> git add . – Stage all changes    -> git commit -m "message" – Commit staged changes    -> git commit -a -m "message" – Commit all tracked files directly     ✨ 𝗨𝗻𝗱𝗼𝗶𝗻𝗴 𝗼𝗿 𝗺𝗼𝗱𝗶𝗳𝘆𝗶𝗻𝗴 𝗰𝗵𝗮𝗻𝗴𝗲𝘀     -> git reset – Unstage files from staging area     -> git reset <commit_id> – Move repository back to a specific commit          ✨ 𝗪𝗼𝗿𝗸𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗿𝗲𝗺𝗼𝘁𝗲 𝗿𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝗶𝗲𝘀     -> git clone <repo_url> – Copy repository from remote     -> git push – Upload local commits to remote repository     -> git fetch – Download updates from remote without merging 🔹 𝗦𝗺𝗮𝗹𝗹 𝗯𝘂𝘁 𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀 -> Working Directory → The place where you create and modify project files -> Staging Area → Temporary area where changes are prepared before committing -> Repository → Where Git permanently stores the history of commits -> .git Folder → Created when running git init. It stores all repository metadata, commit history, branches, and configuration. This is essentially the brain of the Git repository. 💡 𝗜𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁: If the .𝗴𝗶𝘁 folder is deleted, the project remains but Git tracking and history are lost. 💡 𝗧𝗼𝗱𝗮𝘆’𝘀 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆 Git is not just about saving code — it’s about managing history and collaborating safely. #DevOps #Git #GitHub #CICD #VersionControl #CloudComputing #DevOpsJourney #LearningInPublic #ContinuousLearning #TechCommunity

Last week I focused on strengthening my Git and GitHub workflow, and it finally started to feel less like commands and more like a system. I worked through the full cycle: Creating repositories (both local and remote) Initializing projects with git init Tracking changes with git add and git commit Syncing work using git pull and git push Cloning repositories and understanding how projects are shared Forking projects and working independently from the original codebase The most interesting part was going deeper into branching strategies: Practicing git merge and understanding how histories come together Using git rebase to keep a cleaner, more linear project history At first, some of these commands felt mechanical. But after repeating them in real scenarios, I started to understand why they matter—especially when multiple changes are involved. One key takeaway: Version control isn’t just about saving code. It’s about managing change without losing clarity. Still learning, still refining—but the foundation is getting stronger. #DevOps #Git #GitHub #VersionControl #LearningInPublic

Day 25 | #90DaysOfDevOps🚀 — Mastering Advanced Git Commands Today I focused on learning and practicing some powerful Git commands that help developers manage code safely and efficiently. Understanding these commands is essential for real-world collaboration and version control. 🔧 What I practiced today: ✅ Git Reset – Learned how to undo commits in different ways: --soft → keeps changes staged --mixed → keeps changes but unstaged --hard → removes commits and deletes changes ✅ Git Revert – Safely undo a commit by creating a new commit without rewriting history. This is the recommended approach for shared repositories. ✅ Handling Merge Conflicts – While reverting a commit, I encountered a conflict and learned how to manually resolve it and continue the revert process. 📚 Updated my Git command reference to include: Setup & Configuration Basic Git Workflow Branching Remote repositories Merging & Rebasing Stash & Cherry Pick Reset & Revert #DevOps #Git #VersionControl #LearningInPublic #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham

🚀 Day 53 – Pulling Changes, Resolving Conflicts & Managing Code Safely 🚀 Today I focused on handling real-world Git challenges — syncing updates, resolving conflicts, and undoing mistakes like a professional developer 💻⚡ 🔹 What I Learned Today ✔ Pull Command git pull → Fetch + merge updates from remote repository Understood how to keep local code in sync with team updates Learned the importance of pulling before pushing ✔ Resolving Merge Conflicts Understood why conflicts occur (same file, same lines changed) Practiced manually resolving conflicts Staged and committed the resolved version This was a big learning moment — conflicts aren’t scary when you understand them 🔥 ✔ Undoing Changes Explored safe recovery techniques: git restore git reset git revert Now I know how to fix mistakes without breaking project history. ✔ Forking Repositories Learned how to fork projects on GitHub to: Contribute to open source Experiment independently Work without affecting the original repository 🔹 Reflection Today made Git feel real and powerful. Version control isn’t just about saving code — it’s about managing collaboration, mistakes, and evolution safely 🧠 Every day, my development workflow is becoming more professional 🚀 #Git #GitHub #VersionControl #MergeConflicts #DeveloperWorkflow #OpenSource #FullStackJourney #100DaysOfCode #TechGrowth 🚀

🚀 Day 51 – Mastering Git Workflow with VS Code 🚀 Today was all about hands-on Git practice inside VS Code, focusing on building a real-world development workflow 🧠💻 From cloning repositories to pushing commits, I strengthened my understanding of how developers manage code efficiently every day. 🔹 What I Practiced Today ✔ Working with Git inside VS Code Learned how to use integrated terminal + source control panel to manage repositories directly from the editor. ✔ Clone & Git Status git clone → Cloning remote repositories git status → Tracking file changes & staging state ✔ Add & Commit Workflow git add . → Staging changes git commit -m "message" → Saving snapshots of work Understanding clean commit practices for readable project history 📜 ✔ Push to GitHub git push → Syncing local changes with remote repositories 🌍 ✔ Repository Initialization git init → Creating a brand new Git repository 🔹 Why This Matters Mastering this workflow means: ✅ Clean version tracking ✅ Safe experimentation ✅ Seamless collaboration ✅ Professional development practices 🔹 Reflection Git + VS Code feels like a powerful developer combo ⚡ Every command I learn improves speed, confidence, and project quality. Next → Branching, merging & conflict resolution 🚀 #Git #VSCode #GitWorkflow #VersionControl #DeveloperLife #FullStackJourney #100DaysOfCode #LearningByDoing #TechSkills 🚀✨