Selective Git Merge with Cherry-Pick in DevOps

🚀 DevOps Journey Update Spent some time revisiting and brushing up on Git & GitHub fundamentals — tools that quietly power almost every modern development and DevOps workflow. Refreshed concepts like: 🔹 Version Control – tracking changes without the “who broke this?” mystery 🔹 Branches – experimenting safely without disturbing main 🔹 Rollback & Revert – the DevOps safety net when things go sideways 🔹 SSH Authentication – secure GitHub access without the password dance 🔹 Tags & Semantic Versioning – keeping releases organized (v1.0.0, v1.1.0, etc.) Also went through the usual Git muscle memory workout: git clone • git add • git commit • git push • git pull • git branch • git merge • git revert It’s interesting how something developers use daily becomes even more important from a DevOps perspective — where traceability, collaboration, and reliable releases really matter. Next in my DevOps journey: Linux Servers 🐧 Time to spend more quality time with the terminal. #DevOpsJourney #LearningInPublic #Git #GitHub #DevOps #Linux

Today was all about Git – the backbone of collaboration in DevOps. Today I learned that DevOps is not just about tools like Docker or Kubernetes… It starts with version control discipline. 🔹 What I Learned Today: ✅ What is Version Control & Why it matters → Tracks changes in code → Enables collaboration → Prevents code conflicts ✅ Difference between: Git (tool) GitHub (platform) GitLab & Bitbucket (alternatives) ✅ Core Git Commands I Practiced: git init git clone git status git add git commit git log git branch git checkout git merge ✅ Understood the concept of: Branching strategy Merge conflicts Pull requests Local vs Remote repositories #Devops #DevOps #Git #Linux #Github #bash

🚀 Automating Releases with Git Hooks | Day 34/100 – DevOps Journey Today’s task in my 100 Days of DevOps challenge was focused on something very practical in real DevOps workflows — automating release tagging using Git hooks. The requirement was to merge a feature branch into master, but before pushing changes, configure a post-update hook that automatically creates a release tag whenever updates are pushed to the master branch. 🔹 What I worked on: - Merged feature branch into master - Created a post-update Git hook - Automated dynamic release tag creation using current date format - Tested the hook to ensure it generates release tags correctly - Pushed the final changes safely without altering repository permissions 🔐 Why this matters in real environments: - Automation reduces manual errors. - In production systems, automated tagging helps with: - Release tracking - Deployment traceability - Version management - CI/CD workflows Continuing to build hands-on experience in Git internals, automation, and production-ready workflows, while sharing my learning publicly Github :- https://lnkd.in/gnBnU_cv #100DaysOfDevOps #DevOps #Git #GitHooks #Automation #ReleaseManagement #Linux #CloudEngineering #LearningInPublic #TechCareers #OpenToWork #KodeKloud

🚀 Creating a Docker Image from a Running Container | Day 39/100 – DevOps Journey Today’s task in my 100 Days of DevOps challenge involved creating a Docker image from a running container — a common scenario when developers want to preserve changes made during testing. 🔹 What I worked on: - Identified the running container on the application server - Created a new Docker image from that container - Tagged the image as official:devops for future use - Learned how container state can be captured as an image 🔐 Why this matters in real environments: During development and testing, containers may be modified with new configurations or tools. Creating an image from that container allows teams to: - Preserve the tested environment - Share the setup with other developers - Reuse the configuration for future deployments Continuing to strengthen hands-on skills in Docker, container lifecycle management, and DevOps practices, while sharing my learning publicly. Github :- https://lnkd.in/gnBnU_cv #100DaysOfDevOps #DevOps #Docker #Containerization #Linux #CloudEngineering #LearningInPublic #TechCareers #OpenToWork #KodeKloud

🚀 Day 2 of My DevOps Journey — Git (Where Real Collaboration Begins) Yesterday was Linux. Today, I stepped into Git — the backbone of DevOps workflows. At first, Git felt simple… until I actually started working with it. 🔹 What I Practiced: Initializing a repo (git init) Branching strategy (main, feature/*) Merging vs Rebasing Fixing merge conflicts Using git stash when switching work Writing meaningful commit messages 🔹 Real Challenge I Faced: I accidentally: ❌ Made changes on the wrong branch ❌ Used stash incorrectly ❌ Faced merge conflicts And honestly… this is where real learning started. 🔹 What I Learned: ✔ git rebase helps keep history clean ✔ Merge conflicts are not errors — they are decisions ✔ Commit messages matter more than we think 💡 Key Learning: “Git is not about commands. It’s about thinking in versions.” I also practiced: Squashing commits using interactive rebase Understanding how teams collaborate using PRs This felt like a big step toward real-world DevOps work. Next → Docker (containers, images, real deployment) If you’ve struggled with Git before, you’re not alone. Let’s grow together 🤝 #DevOps #Git #VersionControl #Cloud #LearningInPublic #BuildInPublic #CI_CD

🔧 DevOps Practice: Cleaning Up Git Test Branches Today, day 5/5, I completed a hands-on Git task in the KodeKloud Stratos Datacenter environment that focused on maintaining a clean repository by removing unused test branches. 📌 Task Objective The Nautilus development team had created several temporary branches during testing in the repository located at: /usr/src/kodekloudrepos/blog My task was to delete the branch xfusioncorp_blog from the Git repository on the Storage Server. 🛠 Steps Taken 1️⃣ Connected to the Storage server using SSH 2️⃣ Navigated to the repository directory 3️⃣ Verified existing branches to confirm the target branch 4️⃣ Switched to a different branch (master) because Git does not allow deleting the active branch 5️⃣ Deleted the test branch safely using Git Key Commands Used: ssh natasha@ststor01 cd /usr/src/kodekloudrepos/blog git branch git checkout master git branch -d xfusioncorp_blog ✅ Result The branch was successfully removed, helping keep the repository organized and reducing clutter from temporary development branches. 💡 Key Learning Git will not allow deletion of the branch you are currently on, so switching to another branch first is essential. Consistent repository cleanup is an important practice in DevOps workflows to maintain an efficient development environment. #DevOps #Git #KodeKloud #Linux #CloudEngineering #ContinuousLearning

DevOps Journey – Day Update Today I focused on understanding the fundamentals of Git, a core tool in modern DevOps practices. 🔹 Learned key Git concepts: - Working Directory, Staging Area, Repository - git add → staging changes - git commit → saving changes to repository - git status → tracking file states - git log & git log -2 → viewing commit history 📌 Understanding Git workflows is essential for version control, collaboration, and CI/CD pipelines. Excited to continue building strong DevOps fundamentals step by step! #DevOps #Git #Linux #LearningJourney #CareerGrowth

🚀 New Blog Published: From Git Basics to GitHub Workflows – A DevOps Perspective In my DevOps learning journey, after exploring Linux and Computer Networking, the next important tool I focused on was Git and GitHub. Version control plays a huge role in modern development and DevOps workflows. Whether it’s managing application code, infrastructure as code, or collaborating with teams, understanding Git is essential. In this blog, I’ve tried to explain some important Git and GitHub concepts in a simple and practical way, including: • History of Git • File System vs Version Control System • Important Git commands (init, add, commit, status, rm) • Tracking files in Git • Branching and common branching commands • Clone vs Fork • Push & Pull with SSH / PAT • Rebase vs Merge • Stash and Stash Pop • Cherry Picking • Squash Commit vs Merge Commit • Reset vs Revert • Branching strategies • GitHub CLI • Conflict resolution My goal with this blog was to build a clear understanding of how Git and GitHub workflows fit into DevOps practices. If you are learning DevOps or getting started with Git, I hope this blog will be helpful. 📖 Read the blog here: https://lnkd.in/d-rkRngH I’d love to hear your thoughts and feedback! #DevOps #Git #GitHub #VersionControl #LearningInPublic #DevOpsJourney #DevOpsKaJosh #90DaysOfDevOps #Hashnode #TrainWithShubham #ShubhamLondhe

When I first heard “𝗗𝗲𝘃𝗢𝗽𝘀 𝗶𝘀 𝗮 𝗰𝘂𝗹𝘁𝘂𝗿𝗲”, I honestly couldn’t wrap my head around it. At that time, DevOps just looked… intimidating. So many tools. So many concepts. Linux, Git, Docker, CI/CD, Kubernetes, Terraform, Ansible… the list felt endless. It felt like a mountain of things to learn, and I didn’t know where to even begin. So I did the only thing that made sense to me — start small and build step by step. I began exploring each tool one at a time: Linux → Git → Docker → GitHub Actions → Kubernetes → ArgoCD → Terraform → Ansible. And something interesting happened along the way. Each tool didn’t exist in isolation. Every tool complemented the previous one and unlocked the next. Slowly, I started building things: • A 𝗹𝗼𝗰𝗮𝗹 𝗗𝗲𝘃𝗢𝗽𝘀 𝗹𝗮𝗯 — a simple script that spins up a local registry and Kubernetes cluster to experiment freely. • 𝗔𝘂𝘁𝗼𝗞𝘂𝗯𝗲 — an Ansible setup that provisions multiple EC2 instances and turns them into a Kubernetes cluster. • Deployed my real-time chat application on a cloud Kubernetes cluster. • Turned my old PC into a 𝗵𝗼𝗺𝗲 𝘀𝗲𝗿𝘃𝗲𝗿. • Started experimenting with 𝘀𝗲𝗹𝗳-𝗵𝗼𝘀𝘁𝗶𝗻𝗴 — Jellyfin for streaming, backups, and other services. And then I realized something. Every single project I built had one thing in common: I built it to solve my own problems. I wasn’t just learning tools anymore. I was learning how to combine existing systems and software to create solutions that fit my needs. Ubuntu Server. Docker. Kubernetes. Jenkins. Terraform. Self-hosted services. All pieces of a larger ecosystem. And that’s when it finally clicked for me. DevOps isn’t just tools. 𝗗𝗲𝘃𝗢𝗽𝘀 𝗶𝘀 𝗮 𝗺𝗶𝗻𝗱𝘀𝗲𝘁. It’s about curiosity. It’s about automation. It’s about building systems that make your life easier. Most importantly, it's about constantly learning, experimenting, and improving the way things work. And now I finally understand why people say: 𝗗𝗲𝘃𝗢𝗽𝘀 𝗶𝘀 𝗻𝗼𝘁 𝗮 𝗿𝗼𝗹𝗲. 𝗜𝘁’𝘀 𝗮 𝗰𝘂𝗹𝘁𝘂𝗿𝗲. #DevOps #DevOpsJourney #DevOpsCulture #Kubernetes #Docker #GitOps  #InfrastructureAsCode #Homelab #SelfHosting #Linux #ContinuousLearning #CloudNative

✨ Learning + Hands-on Project + Consistency = DevOps Engineer (Dream Job) 🚀 🚀 Strengthening My DevOps Foundations – Linux, Git & Docker Deep Dive After progressing with Ansible automation, I focused on strengthening my core DevOps fundamentals: 🔹 Advanced Git workflows • Branching, merging, rebasing • Cherry-pick, reset vs revert • Interactive rebase & squash • Understanding commit graph (DAG model) 🔹 Linux hands-on practice • File permissions, process monitoring • Service management • System resource analysis using top 🔹 Docker Architecture Practice • Built multi-container application using Docker Compose • Implemented Nginx as a reverse proxy • Explored internal vs external ports • Understood Docker bridge networking • Practiced container isolation and layered architecture Key Takeaway: DevOps is not just about tools — it's about understanding architecture, networking, and system behavior under failure conditions. Continuing to build production-level thinking step by step. #DevOps #Docker #Git #Linux #CloudLearning #Infrastructure #ContinuousLearning