Cloning Git Repos with Submodules Using --recursive Option

🚀 Git Commands — Knowledge-Based Cheatsheet I created this quick visual reference while revisiting core Git concepts and strengthening my understanding of version control fundamentals. It covers essential areas: ✔️ Setup & configuration ✔️ Repository basics (init, clone, commit) ✔️ Branching & merging ✔️ Remote operations (push, pull, fetch) ✔️ Stash & undoing changes ✔️ Diff, tagging, and advanced commands 💡 Key takeaway: Understanding Git is not just about commands — it’s about managing code history efficiently and collaborating with confidence. This cheatsheet is a handy reference for: • Developers • Automation Engineers • Anyone working with version control 📌 Save this for quick reference and continuous learning. #Git #VersionControl #DevOps #SoftwareDevelopment #Learning #CheatSheet

🔧 Git Commands Every Engineer Uses Daily Working with code? Then Git is part of your daily workflow. Here are important Git commands engineers actually use 👇 📂 "git clone <repo_url>" Download a repository to your local system 📋 "git status" Check current changes and branch status ➕ "git add ." Stage all changes for commit 💾 "git commit -m "message"" Save changes with a meaningful message 🚀 "git push" Upload your changes to remote repository ⬇️ "git pull" Get latest updates from remote 🌿 "git branch" View or create branches 🔀 "git checkout branch_name" Switch between branches 🔄 "git merge branch_name" Merge changes from another branch 💡 Key Insight Good Git usage = clean history + better collaboration. #Git #VersionControl #DevOps #SoftwareDevelopment #CloudEngineer #Programming

🚀 This week I focused on learning Git and version control concepts. Initially, Git commands seemed complex 🤯, but organizing them into logical groups made the learning process much more structured and effective 📚 🔹 Basic: init, clone, status, log 🔹 Staging: add, reset 🔹 Commit: saving changes with meaningful messages ✍️ 🔹 Branching: creating, switching, merging branches 🌿 🔹 Remote: connecting to repositories 🔗 🔹 Push/Pull: synchronizing local and remote code 🔄 🔹 Undo: amending and resetting changes ↩️ 🔹 Stash: temporarily saving work 📦 💡 This approach helped me understand not just the commands, but also the workflow behind version control. Consistent practice is helping me build confidence in managing code efficiently using Git 💻 #Git #VersionControl #DevOps #SoftwareEngineering #LearningJourney #ContinuousLearning #TechSkills #CareerGrowth 🚀

🚫 Git is not a file-sharing tool! I’ve seen projects use Git in surprising — and inefficient — ways. One release, one branch? That’s a risky habit, especially if there’s no master (or main) branch. When the current branch becomes the “production” branch, reverting after an issue can be painfully time-consuming. The classic model still wins: keep one main branch where all code merges, while developers work on their own feature branches. ✅ This approach improves accountability, transparency, and collaboration. Everyone knows who did what, what’s finished, and what’s pending. It’s the foundation of clean version control and healthy teamwork. #DevOps #Git #VersionControl #SoftwareDevelopment #BestPractices #Collaboration #Teamwork #CodingStandards #EngineeringCulture

🚀 Master Git in 5 Simple Steps Whether you're a beginner or need a quick refresher, these are the core Git steps you’ll use in almost every project. 🔧 1. Initialize a Repository Start a new project or clone an existing one. git init git clone <url> ✏️ 2. Make Changes Create, edit, or delete files as needed. This is where development happens. 📦 3. Stage Your Changes Prepare files before committing them. git add <file> git add . 💾 4. Commit Changes Save your progress with a meaningful message. git commit -m "your message" Track history anytime with: git log 🌐 5. Push to Remote Upload your changes to GitHub or another remote repository. git remote add <name> <url> git push -u <remote> <branch> 💡 Why This Matters A clean Git workflow saves time, reduces mistakes, and makes collaboration smoother. Once this becomes a habit, version control feels easy. 🚀 #Git #GitHub #Developer #Programming #DevOps #Coding #SoftwareEngineering

🚀 GitLab – Creating a Branch Branching is an essential part of the development process, allowing developers to work independently without affecting the main codebase. In GitLab, a branch represents a separate line of development. The process of creating a branch is simple and structured. First, log in to your GitLab account and navigate to your project under the Projects section. Then, go to the Repository → Branches option and click on New Branch. Enter the branch name and create it. As shown on page 2, once the branch is created, it becomes visible in the repository, enabling developers to manage and track changes separately. 💡 Branching helps teams collaborate efficiently, maintain code stability, and manage feature development seamlessly. #GitLab #DevOps #VersionControl #Git #AshokIT

🚀 Handling Selective Feature Deployment with Git (Real Scenario) Recently, I faced an interesting challenge in our deployment workflow. We had multiple features merged into the UAT branch and already running on the UAT server. However, the requirement was: 👉 Not all features should go to production immediately 👉 Only one specific latest feature needed to be deployed to PROD 👉 The rest should be released later This is a very common situation in fast-paced development environments, but it needs a clean and safe approach. 💡 Solution: Git Cherry-Pick Instead of merging the entire UAT branch into production, I used git cherry-pick to selectively move only the required commit(s) to the PROD branch. ✅ Benefits of this approach: Fine-grained control over deployments Avoids unintended feature releases Keeps production stable Enables faster hotfix or priority feature releases 🛠️ Basic Steps: Identify the commit(s) in UAT Switch to the PROD branch Cherry-pick the required commit(s) Test and deploy safely git checkout prod git cherry-pick <commit-hash> ⚠️ Of course, conflicts can happen — but with careful resolution and testing, this approach works really well for controlled releases. #Git #DevOps #SoftwareDevelopment #Backend #nodejs #Deployment #Engineering #TechTips #Developers #Programming

🚀 Day 6 of #100DaysOfDevOps Challenge Today I explored one of the most fundamental pillars of modern software development — Version Control Systems (VCS) and Git 🔥 📌 Here’s what I learned today: 🔹 What is Version Control System (VCS)? A system that tracks changes in code over time, enabling collaboration, history tracking, and easy rollback when needed. 🔹 Why is it important? ✔️ Maintains complete history of changes ✔️ Enables team collaboration ✔️ Supports branching & experimentation ✔️ Ensures code safety and integrity 🔹 What is Git & Why Git? Git is a distributed VCS known for its speed, flexibility, and powerful branching capabilities. It’s widely used in DevOps and CI/CD pipelines. 🔹 Git Stages Explained: 📂 Working Directory – Where you create/modify files 📌 Staging Area – Where changes are prepared (git add) 📦 Repository – Where changes are permanently stored (git commit) 🔹 Git Lifecycle: Modify ➝ Stage ➝ Commit ➝ Push ➝ Pull 🔹 Linux Commands to Install Git: sudo apt install git -y sudo yum install git -y sudo dnf install git -y 🔹 Git Logs: Tracking history using commands like: git log git log --oneline git log --graph 💡 Key Takeaway: Mastering Git is not optional — it’s a must-have skill for every DevOps Engineer to manage code efficiently and collaborate seamlessly. 📈 Every commit you make is a step closer to becoming a better engineer! 🔥 What’s next? Diving deeper into branching strategies and Git workflows! #DevOps #100DaysOfDevOps #Git #VersionControl #Linux #CloudComputing #SoftwareDevelopment #DevOpsJourney #LearningInPublic #TechGrowth #CI_CD #Automation #Programming #Developers #flm #Engineering #CareerGrowth #OpenSource #TechCommunity #BuildInPublic 🚀

Why Plain Text + Git just works For a long time, documentation lived next to development. Different tools. Different workflows. Often, different levels of quality. But more teams are moving toward something simpler, and more powerful: plain text documentation, versioned in Git. Why? Because documentation starts behaving like code: - Versioned - Reviewable - Collaborative - Traceable Instead of static pages, you get a living system that evolves with your product. No proprietary lock-in. No disconnected workflows. Just documentation that stays relevant. Is your documentation versioned, or just stored? #Documentation #Git #DevOps #Elevatic

💡 Git Tip: Cherry-Pick – Copy Only What You Need! In real-world projects (especially in automation & CI/CD pipelines), we often face situations like: 👉 A code fix is done in one branch, but urgently needed in another 👉 You don’t want to merge the entire branch (to avoid unwanted changes) 👉 You just need that one specific commit That’s where cherry-pick becomes a lifesaver. 🔧 What it does: It allows you to pick a specific commit from one branch and apply it to another branch. 🧠 Basic usage: git checkout target-branch git cherry-pick <commit-hash> 🚀 Why it’s powerful: ✔ Avoids unnecessary merges ✔ Helps in hotfix scenarios ✔ Keeps branches clean and controlled ✔ Saves time during production fixes ⚠️ Be careful: Cherry-picking creates a new commit → so overusing it can make history messy if not handled properly. 💭 In automation projects, this is super useful when a small fix in test scripts or pipeline config needs to be quickly applied across branches without disturbing ongoing work. #Git #VersionControl #AutomationTesting #SDET #DevOps #SoftwareTesting #Learning