Search for a command to run...
Series
A practical series on learning GitHub Actions step by step. From writing your first workflow to deploying Docker containers and Terraform, this series will cover everything you need to build powerful CI/CD pipelines.
Welcome to the very first day of my GitHub Actions Journey!Over the next weeks, I’ll be diving deep into CI/CD automation with GitHub Actions and documenting my learning through daily blogs. If you’ve ever wondered how to automate workflows, deploy a...
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:...
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...
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...
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...
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...
