Dhanush Boopathi’s Post

🧩 Day 28 of #100DaysOfDevOps — Selective Commit Merging in Git “Excellence is not being the best; it is doing your best in every situation.” — John Wooden Today’s challenge revolved around a real-world Git scenario — merging a specific commit from one branch to another without affecting the rest of the work in progress. Here’s the situation: The Nautilus application development team had a repository located at: 📍 /opt/cluster.git (cloned under /usr/src/kodekloudrepos on the Storage Server in Stratos DC). The repository contained two branches: master (main production branch) feature (active development branch) One developer had made several updates in the feature branch, but only one specific commit — identified by the message “Update info.txt” — was ready to be merged into production. As part of the DevOps team, I: Switched to the master branch to prepare for integration. Identified the target commit on the feature branch using git log. Used a cherry-pick merge to pull only that single commit into master. Verified the merge integrity and ensured no conflicts. Finally, pushed the changes back to the remote repository for deployment readiness. This task perfectly illustrated how precision control in Git can streamline workflows — merging only what’s needed, when it’s needed. In fast-paced DevOps environments, such selective merging avoids instability while keeping production agile and safe. #100DaysOfDevOps #Day28 #Git #GitCherryPick #VersionControl #DevOpsJourney #ContinuousIntegration #SoftwareEngineering #GitOps #TeamCollaboration #TechCommunity #EngineeringExcellence #InfrastructureAutomation #DevOpsCulture #CodeManagement #OpenSource #LearningEveryday #ProblemSolving #CommandLine #CloudComputing #ProfessionalGrowth #AutomationEngineer

🚀 Day 31 of #100DaysOfDevOps – Git Stash Today’s focus was on mastering Git Stash, a powerful feature for managing in-progress work without losing context. The Nautilus development team had previously stashed some unfinished changes in their repository located at /usr/src/kodekloudrepos/news. My task: restore the stashed changes identified as stash@{1} and push them to the remote repository. Steps followed: Checked all stashes using git stash list Applied the required stash with git stash apply stash@{1} Verified the recovered file welcome.txt Committed the change with the message “Added stash 1” Pushed the update to the origin branch Key takeaway: Git Stash acts as a temporary workspace buffer, allowing developers to context-switch effortlessly without losing progress — an essential skill in real-world DevOps environments. "Efficiency is doing things right; effectiveness is doing the right things." – Peter Drucker #Git #DevOps #GitCommands #VersionControl #DevOpsJourney #100DaysOfDevOps #LearningInPublic #CloudOps #ContinuousIntegration #SoftwareDevelopment #GitTips

# DevOps: Day 13 - Git branching strategy Branching strategy is where you have various branches such as: - Master Branch: kept for active development. - Feature Branch: used to introduce new breaking changes. - Release Branch: the branch where our application is built from. Runs end to end functionality test from this branch. So This branch is used to test before releasing to the customer whenever a feature is ready to be released. So here the development work is done, hence it is separated from the master because there will still be active developments going on in the master branch. Which we don't want in the release branch. Release always happens from the release branch. Note: There can also be Bugfix/Hotfix in Git Branching Strategy, just that those are usually short-lived. #DevOps #Tech #git #github #gitbranch #master #feature #release

Day 28 of #100DaysOfDevOps — Understanding Git Cherry-Pick In collaborative projects, not every branch is ready for merging. Sometimes, you only need one specific change from another branch — that’s where git cherry-pick shines. What is Git Cherry-Pick? git cherry-pick allows you to apply a specific commit from one branch onto another without merging all the commits. This is especially helpful when:  You want to move a hotfix or bug patch to the main branch.  You only need a specific update from an experimental branch.  You want to control exactly what goes into production. Basic Syntax: git checkout <target-branch> git log <source-branch> git cherry-pick <commit-hash> git push origin <target-branch> Example: git checkout master git log feature git cherry-pick abc1234 git push origin master As a DevOps engineer, understanding Git’s branching and commit management tools is essential for maintaining clean, stable, and traceable code releases. Cherry-picking ensures precision — you can promote tested fixes to production without merging incomplete features. I found this Medium post by Amir Mustafa helpful: https://lnkd.in/dNzH3n8W #Git #DevOps #100DaysOfDevOps #KodeKloud #VersionControl

🔥 Git Tags — The Hidden Power Behind Safe Rollbacks in Production! Ever deployed something that broke production? 😅 Don’t panic — if your team uses Git tags smartly, rolling back is just a command away! In real DevOps pipelines, Git tags act like “restore points” for your production releases. They help you track what exact version was deployed, automate rollbacks, and maintain clean release histories. Here’s how top teams use them 👇 🔹 1. Tag every release build Before deploying to prod, create a lightweight or annotated tag: git tag -a v2.3.0 -m "Production release v2.3.0" git push origin v2.3.0 🔹 2. Link Git tags to your CI/CD pipeline Your Jenkins or GitHub Actions can auto-deploy when a tag is pushed: on: push: tags: - 'v*' 🔹 3. Rollback instantly If something goes wrong: git checkout v2.2.0 Redeploy that stable version — no guesswork, no chaos. 🔹 4. Track rollback history Tags + release notes = versioned documentation for audits. ✨ Pro Tip: Use Semantic Versioning (v1.2.3) for clarity — makes tracking easier across builds and environments. In production, Git tags = version control + deployment safety 💪 Next time something breaks, your tag will save the day! #Git #DevOps #CI/CD #GitHub #Jenkins

Day 24 of My DevOps Journey Wrapping up my learnings on Vagrant today and moving forward to one of the most essential tools in DevOps: Git Vagrant Recap Over the last few days, I explored how Vagrant helps in creating and managing virtual environments that are: ✅ Consistent across systems ✅ Easy to configure and destroy ✅ Great for testing and automation With Vagrant, I learned to: Initialize and configure environments using Vagrantfile Automate provisioning with tools like Ansible Use private networks and synced folders efficiently Key Takeaway: Vagrant makes environment setup repeatable, reliable, and developer-friendly — the perfect foundation before diving into containerization (Docker). 🔀 Next Stop: GIT — The Version Control Backbone Now stepping into Git, the most powerful and widely used version control system in DevOps. What I’ll Be Exploring Next: What is Git and why DevOps relies on it Key Git concepts — repo, branch, commit, merge Common Git commands How teams collaborate using Git + GitHub Tip: If DevOps is the engine, Git is the version control steering wheel that keeps everything aligned and traceable. Which Git command do you use the most — commit, merge, or rebase? 🤔 #Day24 #DevOpsJourney #Vagrant #Git #VersionControl #Automation #Linux #CloudComputing #InfrastructureAsCode #DevOps #LearningInPublic #ContinuousLearning #GitHub #TechLearning

What Is a Branching Strategy in Git? (2025 Guide) 💡 Ever pushed directly to main and instantly regretted it? 😅 It’s time to get serious about Git Branching Strategies the backbone of modern DevOps, CI/CD, and code collaboration. In this new 2025 guide, we break down how branching defines your entire workflow from hotfixes to release pipelines. 🔹 Learn about: Git Flow vs. GitHub Flow vs. Trunk-Based Development When to merge, when to rebase, and when to hold off Feature branching & environment-based branching Best practices for enterprise CI/CD alignment Tools to automate merge approvals & pull requests 🧠 A strong branching strategy isn’t just for version control . it’s about speed, stability, and scalability in your delivery lifecycle. 📘 Read the complete guide: https://lnkd.in/dCHhU_mP #Git #BranchingStrategy #DevOps #VersionControl #GitHub #GitLab #CloudComputing #SoftwareEngineering #CodeManagement #ContinuousIntegration #ContinuousDelivery #DeveloperTools #CodeReview #CICD #Automation #OpenSource #TechCommunity #PlatformEngineering #Programming #SoftwareDevelopment #AgileDevelopment #SRE #CodingBestPractices #InfrastructureAsCode #CloudEngineering #LinuxCloud #TechInnovation #EngineeringCulture #BuildAutomation #DeveloperProductivity

💡The .gitignore file in Git helps you keep your repo clean by excluding unnecessary files like logs, temporary files, build outputs, or system-generated files from being tracked. It’s a simple yet powerful way to maintain a professional and clutter-free project repository. 🚀 #DevOps #Git

In real-time projects, Git is our best friend — but sometimes it becomes a puzzle! Here are some common Git issues teams face in day-to-day DevOps work 👇 🚫 Merge Conflicts — when multiple people change the same file or line. 💥 Detached HEAD State — happens when you checkout a commit instead of a branch. 🔁 Rebase gone wrong — leads to overwritten commits or lost changes. 🕵️ Wrong branch commits — pushing code to main instead of your feature branch. 🔒 Permission errors — while pushing or pulling due to access or SSH key issues. ✅ Tip: Always take a backup branch before doing a rebase or reset, and pull the latest changes before committing. Git is powerful — mastering it saves hours in debugging and helps maintain clean version control in any DevOps pipeline. #Git #GitHub #DevOps #VersionControl #CICD