Git Basics for DevOps with 90 Days of DevOps

🚀 Day 2/30 – Version Control with Git Continuing my 30 Days of DevOps Challenge 💻 🔍 What I learned: Version control systems like Git help track changes in code, collaborate with teams, and maintain a history of every update. 🔑 Key concepts: • Repositories (Repo) • Commits (Snapshots of code) • Branching (Work without affecting main code) • Merging (Combine changes safely) 💡 Key takeaway: Git makes collaboration safe, structured, and efficient — no more “final_final_v2” files 😄 📌 Small step today, big impact in real-world projects! #DevOps #Day2 #Git #VersionControl #LearningJourney #Cloud

Getting Started with GitHub Actions – My First Steps I recently started working with GitHub Actions and wanted to share a quick beginner-friendly overview for anyone getting started in DevOps or CI/CD. 🔹 What is GitHub Actions? GitHub Actions is a CI/CD tool that allows you to automate workflows directly from your repository. 🔹 Basic Concepts: • Workflow → Defined in .github/workflows/ • Events → Trigger (push, pull_request, etc.) • Jobs → Set of tasks running on a runner • Steps → Individual commands inside a job 🔹 Simple Example Workflow: name: CI Pipeline on: push: branches: [ "main" ] jobs: build: runs-on: ubuntu-latest steps: - name: Checkout code uses: actions/checkout@v3 - name: Run a script run: echo "Hello, GitHub Actions!" 🔹 Why use GitHub Actions? - Seamless GitHub integration - Easy automation - Supports multiple environments - Great for CI/CD pipelines This is just the beginning. The next step is integrating with Docker, AWS, and Terraform #DevOps #GitHubActions #CICD #Automation #Cloud #AWS

Pushed AWS credentials to GitHub by mistake? It happens. But it should never happen twice. Fix it at the system level by installing the git-secrets pre-commit hook so it never reaches GitHub in the first place. > brew install git-secrets ( use os specific cmd) > git secrets --install > git secrets --register-aws This installs a pre-commit hook that scans every commit for AWS credentials and blocks the push if it finds any. This one-time setup saves you the pain of rewriting git history. ————- Want to get better at Devops and SRE? Subscribe to my Devops newsletter for real world content around Devops & SRE https://lnkd.in/gaca-kQS

🚀 Starting My DevOps Journey with GitHub Actions! Today, I’m officially beginning my deep dive into ⚙️ GitHub Actions — one of the most powerful tools for automation in DevOps. Here’s what I’ll be mastering step by step 👇 📌 My Learning Roadmap: 1️⃣ Understanding Git & GitHub fundamentals 2️⃣ Exploring GitHub Actions & its core concepts 3️⃣ Learning workflows, jobs, and steps 🧩 4️⃣ Deep dive into runners 🖥️ 5️⃣ Implementing DevSecOps integrations 🔐 6️⃣ Building complete CI/CD pipelines 🔄 7️⃣ Working with OCI standard pipelines 📦 8️⃣ Troubleshooting real-world issues 🛠️ 9️⃣ Managing GitHub organizations 🏢 🔟 Creating and managing centralized pipelines 🎯 💡 My goal is simple: 👉 Move from beginner to confidently building real-world CI/CD pipelines I’ll be sharing everything I learn along the way — practical, simple, and beginner-friendly 💯 📺 I also have a YouTube channel where I’ll be posting step-by-step tutorials 👉 If you want to learn DevOps in a simple way, don’t forget to subscribe 🙌 YouTube Channel To Follow https://lnkd.in/dnZTSrhG 🔥 Let’s grow together in this DevOps journey! #DevOps #GitHubActions #CICD #Automation #LearningInPublic #Cloud #BeginnerToPro #TechJourney

Week 4, Day 12 of my Cloud Computing journey with TechCrush Today marked an important step forward as we dove into the Git and GitHub workflow — the backbone of modern collaboration in software and cloud development. We also explored the fundamentals of CI/CD (Continuous Integration/Continuous Deployment) and how pipelines automate testing, building, and deployment processes for faster, more reliable releases. To make the concepts stick, here are some of the essential Git commands we worked with and what they do: ✅git init — Initializes a new local Git repository in your project folder. ✅git clone <repository-url> — Creates a local copy of a remote repository (e.g., from GitHub) so you can start working on it. ✅git add . — Stages all your changes (new, modified, or deleted files) for the next commit. ✅git commit -m "Your meaningful message" — Saves your staged changes to the local repository history with a clear description. ✅git push origin main (or your branch) — Uploads your committed changes to the remote GitHub repository. ✅git pull origin main — Fetches and merges the latest changes from the remote repository to keep your local copy updated. ✅git branch and git checkout -b <branch-name> — Creates and switches to a new branch for isolated feature development (a best practice to avoid messing with the main codebase). We wrapped up the session with our bi-weekly assessment, and I'm happy to report it went very well!😎 Grateful for these sessions that are building a strong foundation in cloud technologies and DevOps practices. #CloudComputing #Azure #Git #GitHub #CICD #DevOps #LearningInPublic #TechJourney

Still pushing on this Tech Journey folks… Here’s 🚀 Day 20 of My Cloud Computing & DevOps Journey The focus was on Git Workflow & how code moves from your system to the cloud 💻☁️ 🔄 Understanding Git Workflow When working on a project with Git, your code doesn’t just magically appear online, it passes through different stages: 🖥️ 1. Local Working Directory This is where you write and edit your code.
Think of it as your workspace. 📥 2. Staging Area Before saving changes, you select what should be tracked using: git add It’s like preparing files before officially saving them. 📦 3. Local Repository This is where your changes are committed and stored locally: git commit -m "your message" Now your work has a version history 📜 🌍 4. Remote Repository This is where collaboration happens!
You push your code to platforms like GitHub or Azure DevOps: git push Now your team (or the world 🌎) can access your work. 🔁 Full Flow (Simple Visualization) 💻 Code → 📥 Stage → 📦 Commit → 🌍 Push 💡 Why This Matters * 👥 Enables team collaboration from anywhere * 🕒 Keeps full history of your project * 🔁 Makes it easy to fix mistakes (rollback) * 🚀 Forms the foundation of CI/CD pipelines 💭 My Takeaway:
Understanding Git workflow is like learning how to properly save, track, and share your work — a must-have skill for every DevOps engineer. #DevOps #Git #CloudComputing #AzureDevOps #LearningInPublic 🚀💻

Day 7 of My DevOps Journey: Introduction to Docker 🐳🚀 Today I learned about Docker, a powerful tool used in DevOps for containerization. 🔹 What is Docker? Docker is a platform that allows developers to package applications and their dependencies into containers. 🔹 Why Docker is important? ✅ Works on any system ✅ Lightweight compared to virtual machines ✅ Fast deployment 🔹 Key Concepts: 📦 Container – Runs application 🖼️ Image – Blueprint of container ⚙️ Docker Engine – Runs containers 🔹 Basic Commands I explored: 🚀 docker run – run container 📥 docker pull – download image 📋 docker ps – list containers Learning Docker feels like a big step towards real-world DevOps practices 💪 #DevOps #Docker #Containerization #LearningJourney #Cloud

Reflecting on My CI/CD Mastery: Jenkins, Bitbucket, and Helm for Cloud Architects Jenkins: Built multi-branch pipelines with declarative syntax, integrating plugins like Pipeline and Blue Ocean. Automated builds, tests, and deployments—slashing release cycles by 40% in my projects. Bitbucket: Leveraged Pipelines for YAML-based workflows, Git LFS for large repos, and webhooks for seamless Jenkins triggers. Perfect for team collab in agile cloud migrations. Helm: Charted Kubernetes apps like a pro—custom values.yaml, templating secrets, and upgrades via helm upgrade. Deployed microservices on EKS/AKS with zero-downtime rolling updates. These tools are the backbone of modern DevOps! #CloudArchitecture #DevOps #Jenkins #Bitbucket #Helm #Kubernetes #CI_CD #AWSCertified

Over the past few days I have been working on a Kubernetes GitOps pipeline as part of building my DevOps portfolio from the ground up. The core idea behind the project was simple — Git should be the single source of truth for everything that runs in the cluster. No manual kubectl apply, no direct cluster changes. You commit to main, ArgoCD detects it within minutes and syncs the cluster automatically. The setup includes Helm for packaging and versioning the application, ArgoCD for continuous delivery, Prometheus and Grafana for full cluster observability, and a GitHub Actions CI pipeline that validates every Helm chart and Kubernetes manifest using kubeconform before anything gets near the cluster. The part that stuck with me was the selfHeal flag in ArgoCD. If someone manually changes something directly in the cluster, ArgoCD detects the drift and reverts it back to match Git automatically. That single feature changes how you think about cluster management entirely. GitHub :- https://lnkd.in/gasSZU-d #DevOps #Cloud #Git #ArgoCD #Kubernetes #Automation #GitOps

🚀 Day 7 of My DevOps Journey — GitHub Webhooks (Real-Time CI/CD) Until now, I was triggering Jenkins pipelines manually. Today, I automated the trigger itself. 👉 Push code → Pipeline runs automatically This is what real DevOps looks like. 🔹 What I Practiced: - Setting up GitHub Webhooks - Connecting GitHub → Jenkins - Configuring webhook triggers in pipeline - Testing end-to-end automation 🔹 Mini Project: I implemented a real-time CI/CD flow: ✔ Pushed code to GitHub ✔ Webhook triggered Jenkins build instantly ✔ Pipeline executed automatically ✔ Docker image built & deployed No manual steps. Fully automated 🔥 🔹 Real Issues I Faced: ❌ 403 error (No valid crumb included) ❌ 400 error (Bad webhook request) 🔹 How I Fixed It: ✔ Configured Jenkins security settings (CSRF / crumb issue) ✔ Verified webhook URL & payload ✔ Used tools like ngrok for local webhook testing 💡 Key Learning: “DevOps is not about speed — it’s about automatic reliability.” Now I understand: - Event-driven automation - How real CI/CD pipelines are triggered - Importance of secure integrations Next → AWS EC2 Deployment (taking pipelines to cloud ☁️) If you're building in DevOps, let’s connect 🤝 #DevOps #Webhooks #Jenkins #CICD #Automation #Cloud #AWS #LearningInPublic