Refreshing Git Fundamentals for Collaborative Development

🚀 𝟗𝟎 𝐃𝐚𝐲𝐬 𝐨𝐟 𝐃𝐞𝐯𝐎𝐩𝐬 | 𝐋𝐞𝐚𝐫𝐧𝐢𝐧𝐠 𝐢𝐧 𝐏𝐮𝐛𝐥𝐢𝐜 | 𝐇𝐚𝐧𝐝𝐬-𝐎𝐧 | 𝐏𝐫𝐨𝐣𝐞𝐜𝐭𝐬 🌳 Branching out into Version Control: My First Git Repo! Day 22 of #90DaysOfDevOps is done! ✅ Today, I transitioned from scripting to mastering Git—the absolute backbone of DevOps and modern software engineering. 👨💻 I set up my global config, initialized my first repository, and got hands-on with the core workflow: Working Directory ➡️ git add (Staging) ➡️ git commit (Repository). ✅ git init → git add → git commit → Repeat! 💡 Biggest Aha! Moment: Understanding the Staging Area. It isn’t just an extra annoying step; it’s a drafting space that lets you group related changes together before sealing them into a commit, keeping the project history clean and logical! 🔗💻 GitHub Repo: https://lnkd.in/dZsmFiQT #90DaysOfDevOps #DevOpsKaJosh #TrainWithShubham #Git #GitHub #VersionControl #DevOpsJourney

Day 24 of learning and practicing DevOps 🔁 Worked on advanced Git concepts -- Worked on: • Merging branches (fast-forward vs merge commit) • Handling merge conflicts and resolving them manually • Understanding rebase and how it rewrites history • Squash vs regular merge for clean commit history • Using git stash to manage work-in-progress • Applying cherry-pick for selective commits Important part: once understood the flow: edit → add → continue It became clear that Git is not complicated — it’s just strict about tracking changes. Learning today --> history matters Merge keeps history Rebase rewrites history depends on the situation. Here are my notes: https://lnkd.in/gWM2ZrM2 📍 #DevOps #Git #VersionControl #GitHub #LearningInPublic #90DaysOfDevOps #TrainWithShubham

* Git Merge vs Rebase in GIT While working with Git, understanding merge and rebase is very important. 📌 git merge → Combines branches → Keeps full history → Creates a merge commit 📌 git rebase → Moves your changes on top of another branch → Keeps history clean → No extra merge commit ⚡ Key Difference Merge = Safe & complete history Rebase = Clean & linear history 🚀 Why it’s important? ✔ Helps manage code properly ✔ Makes debugging easier ✔ Used in daily development work 💡 Simple Tip Use merge for team/shared branches Use rebase for cleaning your local commits Let’s keep learning and growing 🚀 #Git #DevOps #Learning

📌 Git Cheat Sheet — Saved this for daily use Going through this reminded me of something simple but powerful: Git isn’t just about commands — it’s about how we manage code and collaborate effectively. 💡 What stood out to me: You don’t need to know everything at once. Mastering the basics like init, add, commit, and push already puts you ahead. As you move into branching, merging, and advanced workflows, things can feel a bit confusing 😅 — but that’s exactly where real learning begins. Small improvements in how we use Git can completely transform team productivity. 👇 Curious to hear from you: Which Git command or workflow do you use the most? #Git #DevOps #VersionControl #SoftwareDevelopment #Coding #LearningInPublic

Pushing code is easy… making it run automatically is the real game 🤯 Day 18 of my DevOps Journey 🚀 Today I learned how to integrate Git with Jenkins — and this is where things start getting real. Instead of just storing code in GitHub, I connected a public repository to Jenkins and triggered a build pipeline. From creating a freestyle job → linking the Git repo → installing Git on the server → running “Build Now”… I was able to see my code being pulled and executed automatically. That moment when the build shows SUCCESS ✅ That’s when you realize DevOps is not theory anymore. Key learning: Code + Automation = Real DevOps This is just the beginning — next step is automating this entire flow without clicking anything manually ⚙️ Have you ever triggered your first build in Jenkins? How did it feel? 👇 #DevOps #Jenkins #Git #CICD #LearningInPublic #100DaysOfDevOps #Day18

🚀 Deep diving into Git concepts as part of my DevOps journey! Here’s what I worked on: 🔹 End-to-end Git workflow (clone → add → commit → push) 🔹 Branching strategies used in real projects 🔹 Merge techniques (Fast-forward, Recursive, Rebase) 🔹 Handling merge conflicts like a pro 🔹 Using stash, revert, reset for better control 🔹 Pull Requests for team collaboration 💡 Key takeaway: Git is not just a tool—it’s the foundation of CI/CD and team collaboration. Excited to apply these concepts in real-world projects and pipelines! #DevOpsEngineer #GitHub #CI_CD #Automation #LearningJourney

Git Series | Day 3 🔄 I used to think merging branches was complicated. Turns out, sometimes Git just... slides. Today I learned about Fast-Forward merges — and it genuinely changed how I think about branch history. Here's the simple mental model: → You create a feature branch off master → You do your work (f1, f2) → Meanwhile, master hasn't moved → Git doesn't need a new commit — it just moves the master pointer forward to f2 That's it. Clean. Linear. No mess. Why does this matter in DevOps? In a CI/CD pipeline, a clean git log isn't just aesthetic — it's operational. Auditing deployments, tracing bugs, rolling back changes — all of it gets harder when your history is tangled. Fast-forward = linear history = fewer headaches in production. Day 3 done. Building one concept at a time. 🚀 #Git #DevOps #100DaysOfCode #VersionControl #CI/CD

Ever noticed this? 😄 ✈️ git commit – smooth, controlled, everything looks fine 🚀 git push – boom! things go live 👥 git add . – adding EVERYTHING like there’s no tomorrow 😂 This meme perfectly captures a common developer habit… We carefully commit changes… We confidently push them… But when it comes to staging, we go all in with git add . 😅 👉 Reality check: Blindly adding everything can sometimes push unwanted files, secrets, or bugs. 💡 Best Practice: Be intentional. Use: • git add <file> • git status before commit Because in DevOps & development… small discipline = big stability #Git #DevOps #ProgrammingHumor #SoftwareEngineering #DeveloperLife

I just built my first CI/CD pipeline from scratch. It broke 10+ times before it worked. Here's what happened. As part of my DevOps bootcamp (TechWorld with Nana), I set up a complete Jenkins pipeline for a NodeJS application. The goal: every code change should be automatically tested, built into a Docker image, pushed to Docker Hub, and versioned — no manual steps. The setup: • Ubuntu VM running on VirtualBox • Jenkins running as a Docker container with the host's Docker socket mounted • Jenkinsfile defining 5 pipeline stages: version bump, test, build, push, commit • GitLab for source code, Docker Hub for images What went wrong (and what I learned): First, GitLab authentication broke the pipeline. My password had special characters that mangled the git URL. The fix: use a Personal Access Token instead. Lesson — never use passwords with special characters in CI/CD URLs. Tokens are safer and cleaner. Then, Jenkins couldn't build Docker images. "Permission denied" on the Docker socket. Even though the socket was mounted, Jenkins runs as a non-root user. The fix: chmod 666 on the socket inside the container. Lesson — mounting a socket isn't enough, the permissions have to match. The result: a fully automated pipeline that increments the app version, runs tests (pipeline stops if tests fail), builds a Docker image with the new version tag, pushes it to Docker Hub, and commits the version bump back to GitLab. One command triggers all of this. That's CI/CD. Biggest takeaway: CI/CD isn't just about writing a Jenkinsfile. It's about understanding how Jenkins, Docker, Git, and your application all connect. You're the bridge between all these tools. Module 8 progressing. Still building, still breaking things, still learning. #DevOps #Jenkins #CICD #Docker #Pipeline #GitLab #Automation #LearningInPublic #CareerChange #TechWorldWithNana

🚀 Git vs GitHub — Stop Confusing These Two If you’re serious about becoming a developer, you need to understand this clearly. 🔹 Git A 𝗱𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗲𝗱 𝘃𝗲𝗿𝘀𝗶𝗼𝗻 𝗰𝗼𝗻𝘁𝗿𝗼𝗹 𝘀𝘆𝘀𝘁𝗲𝗺 that runs on your machine. ✔ Tracks every change in your code ✔ Works offline ✔ Maintains full version history ✔ Enables branching & merging 👉 Git is the 𝗰𝗼𝗿𝗲 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆 𝗯𝗲𝗵𝗶𝗻𝗱 𝘃𝗲𝗿𝘀𝗶𝗼𝗻 𝗰𝗼𝗻𝘁𝗿𝗼𝗹 🔹 GitHub A 𝗰𝗹𝗼𝘂𝗱-𝗯𝗮𝘀𝗲𝗱 𝗽𝗹𝗮𝘁𝗳𝗼𝗿𝗺 𝘁𝗵𝗮𝘁 𝗵𝗼𝘀𝘁𝘀 𝗚𝗶𝘁 𝗿𝗲𝗽𝗼𝘀𝗶𝘁𝗼𝗿𝗶𝗲𝘀 ✔ Stores your code online ✔ Enables team collaboration ✔ Supports pull requests & code reviews ✔ Integrates with CI/CD & DevOps tools 👉 GitHub is where teams 𝗰𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗲 𝘂𝘀𝗶𝗻𝗴 𝗚𝗶𝘁 💡 In Simple Terms: Git = Tracks your code locally GitHub = Hosts and shares your code globally ⚡ Why This Matters Modern development is not just writing code — it’s about: * Managing changes * Collaborating with teams * Delivering software efficiently Git + GitHub sit at the center of this workflow. 📌 Pro Tip Master Git fundamentals first: 𝗰𝗼𝗺𝗺𝗶𝘁 → 𝗯𝗿𝗮𝗻𝗰𝗵 → 𝗺𝗲𝗿𝗴𝗲 Then use GitHub to: 𝗰𝗼𝗹𝗹𝗮𝗯𝗼𝗿𝗮𝘁𝗲 → 𝗿𝗲𝘃𝗶𝗲𝘄 → 𝗱𝗲𝗽𝗹𝗼𝘆 💬 What confused you more at the beginning — Git or GitHub? #Git #GitHub #SoftwareEngineering #Developers #Programming #DevOps #Coding