💻 - Git Week 2 Day 3 – Ignoring, Viewing & Reverting Changes Today I learned how to manage what Git tracks, view what’s changed, and fix mistakes if something goes wrong. These commands are essential for keeping repositories clean and organised — especially when working in teams or deploying to production. ⸻ 🚫 Ignoring Files with .gitignore Not every file in a project needs to be tracked — things like logs, temporary files, and environment variables should be ignored. You can create a .gitignore file to tell Git which files to skip: Example: echo "*.log" > .gitignore This command creates a .gitignore file and ignores all files ending with .log. You can edit this file manually or create it directly on GitHub before pushing your repository. 🔍 Viewing Changes with git diff Before committing, you can see exactly what’s changed since your last save point: git diff This shows all modified lines that haven’t been staged yet — helpful for reviewing before committing. You can also compare two commits or branches, for example: git diff master This compares your current branch against the master branch. 🧹 Unstaging Files with git restore If you’ve added something by mistake with git add, you can unstage it before committing: git restore --staged file This removes the file from the staging area but keeps your changes safe in the working directory. ⸻ Learning how to ignore, review, and revert changes gave me a much clearer understanding of how Git tracks progress — and how to stay in control of my repository history. ⸻ Next Up: I’ll be diving into remote repositories — learning how to connect local work to GitHub using commands like git remote add, git push, and git pull. If you’re following my DevOps journey, stay tuned for how I connect my local projects to the cloud 🌐 #Git #DevOpsJourney #VersionControl #GitHub #CloudComputing #LearningInPublic

💡 Git vs GitHub — The Most Common Confusion in DevOps Every new developer has faced this question at least once: 👉 “Is Git the same as GitHub?” Let’s clear it up 👇 📂 Git → A version control system that tracks your code changes locally. ☁️ GitHub → A cloud platform built on top of Git for sharing and collaboration. Think of it like a 4-step flow: [Working Directory] → [Staging Area] → [Local Repository] → [Remote (GitHub)] 🔧 Key Git Commands to Know Action Command Meaning Stage git add Move files to staging area Commit git commit -m "msg"Save your snapshot Push git push Upload commits to GitHub Pull git pull Download + merge updates ⚖️ Common Confusions git fetch ≠ git pull → Fetch just downloads, Pull downloads + merges. git merge keeps full history; git rebase creates a linear one. git reset --hard deletes changes; git revert safely undoes them. Mastering these small details makes version control smooth, safe, and powerful. 📘 I recently compiled all of this (with diagrams, examples, and GUI tools) into “Git & GitHub Complete Handbook – Illustrated Edition (2025)” for anyone learning Git the right way — from zero to advanced. Want the handbook or just want to discuss Git workflows? 💬 Comment “Git” below or DM me — let’s grow together 🚀 #Git #GitHub #DevOps #VersionControl #OpenSource #Learning #TechCommunity #YashKumarDubey #cloud #lerners #new #update

🚀 Understanding Git & Its Environments — with a Real-Life Analogy If you’ve ever wondered how code travels from your laptop to the cloud, here’s a simple way to picture it 👇 Think of Git as a smart notebook system 📒 for your coding projects. 🔹 Working Directory – Your desk, where you draft your ideas (write and test code). 🔹 Staging Area – The table beside you — you keep the pages ready to glue (using git add). 🔹 Local Repository – Your personal notebook where you paste the finalized pages (using git commit). 🔹 Remote Repository – A digital photocopy of your notebook on Google Drive (GitHub, GitLab, etc.), shared with your team (using git push). 💻 Typical workflow: git status # Check what changed git add . # Stage changes git commit -m "Added login page feature" git push origin main # Upload to cloud (GitHub) When your teammates make changes, you simply: git pull origin main # Download their updates ✨ In short: Code → Test → Stage → Commit → Push → Collaborate 🤝 This is how teams across the world keep projects organized, traceable, and version-controlled — all thanks to Git. 🧠 Tip: Think of Git as your project’s “time machine” — every commit is a snapshot you can always go back to! #Git #GitHub #DevOps #Coding #VersionControl #SoftwareDevelopment #Programming #CloudComputing #TeamWork #Developers

Day 17: I Designed My Own CI/CD Pipeline Using GitHub Actions Today, I successfully designed and implemented a complete Build → Test → Versioning → Docker → VPS Deployment pipeline for my LMS Backend project using GitHub Actions + Docker + SSH. This workflow helps me ship faster, reduce downtime, and eliminate manual deployment effort. Here’s how each stage works — step by step: ✅ Stage 0 — Build & Test - Checkout source code - Install Node.js dependencies using `npm ci` - Run ESLint to ensure code quality - Execute test suite (skips gracefully if no tests yet) - Compile TypeScript for production-ready output 📌 Goal: Ensure code is clean, stable & build-ready before going further. 🔢 Stage 1 — Auto Versioning If triggered manually → Takes version input Else → Automatically generates a new version (patch bump) Then updates `package.json` and pushes version commit to GitHub ✅ 📌 Every successful release gets a traceable version tag! 🐳 Stage 2 — Docker Build & Push ✅Configure Docker Buildx for multi-platform builds ✅ Login to Docker Hub using GitHub Secrets ✅Build and push Docker image with two tags: ✅ Selected version (example: `v1.2.3`) ✅`latest` tag for production auto updates ✅ Store metadata as artifact for release step 📌 Fast builds thanks to registry-based caching! 🚀 Stage 3 — Auto Deployment to VPS ✅ SSH into server securely using secrets ✅ Create `.env` if missing ✅ Pull new Docker image ✅ Stop & remove older container ✅ Run new container with: - Health checks enabled - Auto restart policy - Mounted logs & uploads  ✅ Prune unused old images 📌 Zero downtime & health-driven deployment success check ✅ 🏁 Stage 4 — Create Git Tag 📍 If deployment is successful ➡️ Create release tag ➡️ Push to GitHub 📌 Deployment must succeed before tagging — safe release guarantee! 🔥 What I Learned ✔️ Advanced GitHub Actions workflow design ✔️ Secure DevOps with secrets & SSH automation ✔️ Dockerized production environment management ✔️ CI/CD as a discipline for real-world reliability ✅ Project Link 🔗 GitHub Repository: 👉 https://lnkd.in/gxpiTNBR #DevOps #CICD #GitHubActions #Docker #Automation #SoftwareEngineering  #BackendDevelopment #NodeJS #CloudDeployment #DockerHub  #ProductionReady #VPS #BuildAndDeploy #TechJourney #LearningInPublic

𝗧𝗶𝗻𝘆 𝗖𝗵𝗮𝗻𝗴𝗲, 𝗕𝗶𝗴 𝗜𝗺𝗽𝗮𝗰𝘁 𝗶𝗻 𝗖𝗜/𝗖𝗗 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲 🚀 Today, I made a small but critical improvement to my GitHub Actions workflow a great reminder that even one line of YAML can make your automation easy and smooth... 🔧 𝗪𝗵𝗮𝘁 𝘄𝗮𝘀 𝘁𝗵𝗲 𝗖𝗵𝗮𝗻𝗴𝗲? I tightened the workflow triggers to run only when relevant files change, cutting down unnecessary pipeline runs. And I added this small but impactful line: 𝘧𝘦𝘵𝘤𝘩-𝘥𝘦𝘱𝘵𝘩: 0 to my actions/checkout step, ensuring the full Git commit history is fetched during each run. 💡 𝗪𝗵𝘆 𝗧𝗵𝗶𝘀 𝗠𝗮𝘁𝘁𝗲𝗿𝘀 By default, GitHub Actions performs a shallow clone fetching only the latest commit. That means there’s no HEAD^ (previous commit) available, which breaks commands like: 𝘨𝘪𝘵 𝘥𝘪𝘧𝘧 𝘏𝘌𝘈𝘋^ 𝘏𝘌𝘈𝘋 or any workflow logic that compares the current commit with its parent. With fetch-depth: 0, we now get the complete Git history, enabling accurate diffs, changelogs, and versioning logic across our pipeline 🧠 𝗞𝗲𝘆 𝗧𝗮𝗸𝗲𝗮𝘄𝗮𝘆 Improving a CI/CD pipeline isn’t always about big refactors or something crazy, sometimes it is about understanding how your tools behave under the hood. One line, one insight, and you’ve just made your automation faster, leaner, and smarter! #DevOps #GitHubActions #CI/CD #Automation #SoftwareEngineering #GitTips #ContinuousIntegration #ContinuousDeployment #YAML #CloudNative #PlatformEngineering #DeveloperExperience #InfraAsCode #PipelineOptimization #BuildAutomation #EngineeringExcellence #TechLeadership #UAE #FeynmanLearns #LearningByDoing

Day-2 🚀 Understanding Git & GitHub in DevOps What is Git? Git is a Distributed Version Control System (DVCS) that allows developers to track changes in their code, collaborate seamlessly, and maintain the full history of a project. Unlike centralized systems, Git gives every developer a complete copy of the repository (including history), making it fast, reliable, and flexible for teamwork. Why Git? (Key Benefits) Distributed Architecture → Every developer has the full repo, so work can continue even offline. Speed → Operations like commit, diff, and log are local and super fast. Branching & Merging → Lightweight branches for experimentation, easy merging later. Collaboration → Works well with platforms like GitHub, GitLab, Bitbucket. Integrity → Every file and commit is checksummed (SHA-1 hash) to ensure data safety. Real-Life Analogy Think of Git like Google Docs for code: Multiple people can work together. Every change is saved and recoverable. You can branch off to experiment without affecting the original document, then merge it back once ready. Popular Platforms using Git GitHub → Community-driven, open-source & collaboration friendly. GitLab → Git hosting + DevOps CI/CD pipelines. Bitbucket → Git hosting with Jira integration. 🔹 GitHub: GitHub is a cloud-based hosting platform for Git repositories. Provides a web-based interface to work with Git easily. Allows developers to share code, collaborate, and contribute globally. Supports pull requests to propose changes before merging. Provides issues & project boards for tracking bugs, tasks, and workflows. Includes code reviews & discussions for better collaboration. Offers GitHub Actions for CI/CD automation (build, test, deploy pipelines). Enables version control + collaboration in one place. Real-Life Analogy Git = Your personal notebook where you write and track changes. GitHub = Google Drive where you upload that notebook so your friends (team) can read, edit, and collaborate on it. In One Line Git = Tool to manage code versioning locally. GitHub = Platform to store, share, and collaborate on that code remotely. ⚙️ Git Commands # Create a project folder mkdir MyProject cd MyProject #Initialize Git git init #Copy repo from GitHub to local git clone <repo_URL> #create new branch for any changes in code(version tagging) and switch to new branch git checkout -b feature-update # Add files git add . # Commit changes git commit -m "Updated feature" #Shows changes and branch info git status #Show Lists branches git branch #Switch branch git checkout branch_name # Connect with GitHub git remote add origin https://github.com/<user>/<repo>.git #View commit history git log #Git #GitHub #DevOps #CI/CD #VersionControl #CloudEngineering     👍

Before submitting your code for review on Github, execute this critical command git rebase -i This will give you an opportunity to take all of the commits you've made in your branch so far and smash them into a single commit. This cleans up your history in the event that the maintainer forgets to squash on merge. You'll be presented with an interactive prompt that allows you to choose which commits you want squashed. Simply replace the first word before each commit with an s or squash to squash that commit. After saving, you'll have an opportunity to write the commit message representing all of the changes. This is a good opportunity to summarize the work completed. I believe most of my followers should know about this but everyone starts somewhere and I am sure some beginners could benefit. _________________________________________ I’ve bundled 𝟱 𝗿𝗲𝗮𝗹-𝘄𝗼𝗿𝗹𝗱 𝗗𝗲𝘃𝗢𝗽𝘀 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 you can do with just your laptop, some curiosity, and a free #𝗔𝘇𝘂𝗿𝗲 or #𝗔𝗪𝗦 account. These aren’t hello-world tutorials, they mirror what DevOps engineers actually do at work: • Provision infrastructure with 𝗧𝗲𝗿𝗿𝗮𝗳𝗼𝗿𝗺 • Automate deployments using 𝗚𝗶𝘁𝗛𝘂𝗯 𝗔𝗰𝘁𝗶𝗼𝗻𝘀 • Run and scale apps with 𝗞𝘂𝗯𝗲𝗿𝗻𝗲𝘁𝗲𝘀 • Monitor everything using 𝗣𝗿𝗼𝗺𝗲𝘁𝗵𝗲𝘂𝘀 & 𝗚𝗿𝗮𝗳𝗮𝗻𝗮 • Manage 𝗺𝘂𝗹𝘁𝗶𝗽𝗹𝗲 𝗲𝗻𝘃𝗶𝗿𝗼𝗻𝗺𝗲𝗻𝘁𝘀 like dev & prod • 𝗦𝘁𝗮𝗿𝘁 𝗵𝗲𝗿𝗲:https://lnkd.in/eS3t5NwE

🚀 GitHub vs Jenkins — What’s the Real Difference? When I started learning DevOps, I asked myself... 🤔 👉 “If I can launch my website from GitHub, then why do I even need Jenkins?” At that time, it sounded like both do the same thing. But later, I learned the real difference 👇 💻 GitHub — “Where your code lives” It’s mainly for storing and managing your code. You can host small static websites (HTML, CSS, JS) using GitHub Pages. But it can’t build, test, or deploy complex applications automatically. ⚙️ Jenkins — “Where your code comes to life” Jenkins is like your personal automation assistant 🤖 The moment you push code to GitHub: ✅ Jenkins pulls the latest code ✅ Builds and tests it automatically ✅ Deploys it on servers like AWS EC2, Docker, or Kubernetes ✅ Sends alerts if anything fails 🚨 💡 In Simple Words: GitHub = Code Storage 🗂️ Jenkins = Code Automation ⚙️ They work together — GitHub handles version control, while Jenkins handles build → test → deploy automatically. 💬 What about you? Have you ever connected GitHub with Jenkins in your project? Share your experience below 👇 #DevOps #Jenkins #GitHub #CICD #Automation #PipelineAsCode #LearningJourney

“Git & GitHub Explained in 30 Minutes – Full Beginner Tutorial (Step-by-Step)” Complete Video: https://lnkd.in/e3SFPa89 “Let’s start with Git. Git is a Version Control System — it keeps track of every change you make in your project. Imagine you’re writing an essay, and you can save checkpoints — ‘Version 1’, ‘Version 2’ — and go back anytime. That’s exactly what Git does for your code.” Show a timeline: v1 → v2 → v3 → rollback to v1 Use “save game” analogy from video games. Key Commands:- git init git add . git commit -m "First commit" git log What is GitHub? GitHub is a website that hosts your Git repositories online. It’s like Google Drive for your code, but way more powerful. * Backup your work * Share code publicly or privately * Collaborate with teams using branches & pull requests GitHub dashboard, repositories, pull request demo git remote add origin <repo-url> git push -u origin main “This command connects your local project to GitHub and uploads it.” git branch feature-1 git switch feature-1 git merge feature-1 Fork a repo → make changes → create a Pull Request → team reviews & merges. Steps: Fork repo Clone locally Create branch Push changes Open Pull Request #Git #GitHub #DevOps #MLOps #CloudComputing #AWS #Azure #GoogleCloud #SoftwareDevelopment #VersionControl #Automation #Programming #OpenSource #TechLearning #DeveloperCommunity

🚀 Just Automated My First CI/CD Pipeline Using GitHub Actions! Ever wondered how your code goes from “push to main” → live on server in seconds? 🤔 That’s exactly what I explored in my latest project — Automating Code Deployment for a Node.js App using GitHub Actions and Docker. 🧑💻 Here’s what I built 👇 🔹 A Node.js demo app 🔹 A .yml workflow in .github/workflows/main.yml 🔹 Pipeline stages: Test → Build → Dockerize → Push to DockerHub → Deploy 🔹 Triggered automatically on every code push 🔹 Secrets securely managed using GitHub Secrets 🔒 🎯 Goal: Understand the complete CI/CD automation process — from writing code to seeing it deployed automatically! 💡 What I learned: ✅ How CI/CD works behind the scenes ✅ What runners, jobs, and steps really do ✅ How to automate Docker build & push workflows ✅ How to handle deployment errors like a pro 😎 🎥 Check out my short demo: “CI/CD using GitHub Actions” (Watch how the entire pipeline automates the deployment process!) Now I’d love to hear from you 👇 💬 Have you tried setting up a CI/CD pipeline before? 💭 What tools do you prefer — GitHub Actions, Jenkins, or GitLab CI? #DevOps #GitHubActions #CICD #Docker #Nodejs #Automation #CloudComputing #LearningByDoing #AdeshJavir #DevOpsJourney