Search for a command to run...
Articles tagged with #devops-journey
If you’ve been following my journey, you know by now that GitHub Actions can automate almost anything. But automation without configuration is like a car without fuel.This is where variables and secrets come in — they allow us to pass dynamic values ...
Contexts are the secret sauce that makes GitHub Actions feel dynamic and smart.They’re how your workflows “know” about the repo, the event that triggered them, the runner machine, step outcomes, and more. If workflows are recipes, contexts are the pa...
Welcome back to Day 05 of our GitHub Actions Journey 👋.So far, we’ve learned about workflows, jobs, events, triggers, and artifacts. Today, we’re tackling something super powerful: Outputs. Think of outputs as a way for jobs and steps to “talk” to e...
Hey everyone 👋 welcome back to my GitHub Actions Journey. Today’s topic is about Job Artifacts – a super useful way to pass files between jobs inside your workflow. 🔹 What Are Job Artifacts? When you run a workflow in GitHub Actions, different jobs...
Yesterday, we built our first CI/CD pipeline for a Node.js app. But an important question remains: 👉 When should these workflows run? That’s where events and triggers come in. ⚡ What Are Events & Triggers? Event → Something that happens in your re...
Welcome back to Day 02 of my GitHub Actions Learning Journey.Yesterday, we covered the basics of workflows, jobs, steps, and triggers.Today, we’ll take things a step further and build a simple CI/CD pipeline for a Node.js project 🚀. 🤔 Quick Recap:...
