Day 4 – Git Basics Today I completed Day 4: Git Basics — an essential tool for every Developer and DevOps Engineer. 🔹 What is Git? Git is a distributed version control system that helps track code changes, collaborate with teams, and manage different versions of a project safely. 🔹 Core Git commands I practiced today: git init → Initialize a new Git repository git add → Stage changes before committing git commit -m "message" → Save changes with a meaningful message Git is the backbone of collaboration in DevOps. Without version control, managing real-world projects becomes difficult and risky. #DevOps #Git #VersionControl #LearningInPublic #Day4 #TechJourney

🚀 Level Up My Version Control Skills in 2026! Just watched the Complete Git and GitHub Tutorial for Beginners 2025 || Zero to Hero Git Master Class 📹 — and it’s a game-changer for anyone starting out with version control or aiming to sharpen their DevOps skills. From setting up Git, learning essential commands, branching, merging, to mastering collaboration with GitHub — this tutorial covers all the fundamentals you need to go from zero to hero in Git & GitHub. Perfect for developers, SDETs, DevOps engineers, and anyone passionate about clean, versioned code. 💡 Whether you’re preparing for your first tech role or reinforcing your foundation in modern development workflows, this resource is worth checking out! I thank Jatin Shharma for providing this valuable content 👉 Watch here: https://lnkd.in/gjGRiKWX #Git #GitHub #DevOps #VersionControl #SoftwareDevelopment #LearningJourney #TechSkills

Day 22 of #90DaysOfDevOps – Building Strong Git Foundations Today I went back to basics and focused on understanding Git properly — not just using it. Instead of only running commands, I took time to understand: How Git tracks changes internally The difference between the working directory, staging area, and repository Why git add and git commit are separate steps What actually lives inside the .git directory How to maintain a clean and meaningful commit history I created a fresh repository from scratch and intentionally built multiple commits to practice structured version control. I also started maintaining a personal git-commands.md reference that I’ll continue updating as I learn more. Key takeaway from today: Version control is not just about pushing code. It’s about maintaining clarity, traceability, and discipline in how changes are made. Strong DevOps workflows start with strong Git fundamentals. Repository updated with Day 22 documentation. #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #Git #VersionControl #DevOps #LearningInPublic

Day 25 of my #90DaysOfDevOps journey Today I explored Git Reset vs Git Revert and understood how to safely undo mistakes in Git. Practiced --soft, --mixed, and --hard resets and learned when each should be used. Compared reset vs revert and understood why revert is safer for shared branches. Also researched branching strategies like GitFlow, GitHub Flow, and Trunk-Based Development. This helped me understand how real engineering teams manage code at scale. 🔗 GitHub Notes: https://lnkd.in/gptC5JTw #90DaysOfDevOps #DevOps #Git #VersionControl #TrainWithShubham #LearningInPublic

Day 12 Of My DevOps Journey 🚀 : Headline : Mastering the Git Lifecycle! 🛡️ Today was all about understanding how Git actually manages our code behind the scenes. It's not just about saving files; it's about the workflow! I learned about the 3 magical stages of Git: 1️⃣ Working Directory:- Where I create/edit my files. 2️⃣ Staging Area:- The "middle ground" where I prepare files for a commit. 3️⃣ Local Repository:- Where my code is securely saved with a unique Commit ID. Understanding the difference between git add and git commit changed my perspective on version control. Now I know how to track every single change in my project! 🔗 Check out my updated Repo: [https://lnkd.in/dkSmqY3u] #DevOps #Git #GitHub #90DaysOfDevOps #TechLearning #CloudComputing #WomenInTech #TechnicalGuftgu

Day 23 | #90DaysOfDevOps 🚀 – Git Branching & Working with GitHub Today I deepened my understanding of Git branching, one of the most powerful concepts in version control. 📌 What I learned: 👉Why branches are used instead of committing directly to main 👉Difference between git switch and git checkout 👉Working with feature branches (feature-1, feature-2) 👉Pushing multiple branches to GitHub 👉Clear understanding of origin vs upstream 👉Difference between git fetch and git pull 👉Clone vs Fork and when to use each Building muscle memory by actually doing things is 🔑 Slowly but surely getting comfortable with real DevOps workflows. #DevOpsKaJosh #Git #GitHub #TrainWithShubham #LearningInPublic

Day 10/100 — Git Branching Strategy finally clicked . Today I learned how real teams manage code using Git branches — and it changed how I see collaboration. Instead of everyone touching the same code line, teams create: Feature branches to build safely Release branches to prepare production Hotfix branches to fix urgent bugs Main branch as the single source of truth The biggest takeaway for me: Good DevOps is not just about tools — it’s about controlled flow of changes. Code doesn’t just get written. It travels through branches before reaching users. Learning step by step. Building in public. Day 10 /100 complete ✅. Follow for Day 11. #Day10 #100DaysOfDevOps #Git #GitBranching #DevOpsJourney #LearningInPublic #BuildInPublic #VersionControl #SoftwareEngineering #DevOpsBasics #BeginnerToDevOps #TechLearning

🚀 Day 22 – My First Git Repository Created! Today I officially started my Git journey 🔥 Git is the backbone of DevOps — every CI/CD pipeline, collaboration workflow, and automation process depends on version control. So today was all about getting comfortable with the fundamentals. 📌 What I Did Today ✅ Installed & configured Git (set up name & email) ✅ Created my first repository: devops-git-practice ✅ Explored the hidden .git/ directory ✅ Created a living reference file: git-commands.md ✅ Made multiple commits with meaningful messages ✅ Built a clean commit history ✅ Understood working directory, staging area & repository 💡 Key Learnings 🔹 git add → Moves changes to the staging area 🔹 git commit → Saves staged changes permanently 🔹 git status → My new best friend 👀 🔹 git log --oneline → Clean way to view commit history 🔹 The .git/ folder → The heart of the repository (delete it and version control is gone!) Understanding the difference between: Working Directory Staging Area Repository …made Git workflow much clearer. 🧠 Biggest Realization Git doesn’t just save files. It saves history. And history = accountability + collaboration + confidence. Small steps, strong foundations 💪 This is just the beginning. Tomorrow we go deeper. #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #Git #VersionControl #DevOpsJourney

Day 2/30 of DevOps Journey – Git Before Git, developers managed code using folders like project_v1, project_final, project_final_final No tracking, no clarity, and risky collaboration. Git solved this by making code tracking and teamwork easy and safe. Check it out here - https://lnkd.in/gf-9UuSg Repost and share for access. #devops #git #justvisualise

🚀 DevOps Basics Series When I first learned Git, I just memorized commands: git add git commit git push git pull But I didn’t really understand what they meant. Once I understood the flow, everything clicked. Here’s the simple version: 🔹 git add → Select the changes you want to track. 🔹 git commit → Save a snapshot of those changes. 🔹 git push → Send them to the remote repository. 🔹 git pull → Get the latest updates from others. That’s it. Modify → Add → Commit → Push → Repeat. And here’s where it gets interesting in DevOps: That one git push can trigger: ✔ Automated tests ✔ Builds ✔ Deployments One command → Entire pipeline starts. Understanding this made Git feel less like commands… and more like a system. #DevOps #Git #LearningInPublic #CI_CD