🚀 Day 01 – Introduction to GitHub Actions: What, Why & How

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 apps, or run tests directly from GitHub – this series is for you.

---

🔹 What is GitHub Actions?

GitHub Actions is a CI/CD (Continuous Integration & Continuous Deployment) tool built right into GitHub.

It allows you to:

• Automate repetitive tasks (build, test, deploy).

• Run pipelines when specific events happen (push, pull request, issue creation, etc.).

• Integrate with cloud providers, tools, and APIs.

In simple words → GitHub Actions is your personal automation engine inside GitHub.

---

🔹 Why do we need GitHub Actions?

Imagine pushing your code and automatically getting:
✅ Tests executed
✅ App built
✅ Docker image pushed
✅ Deployment triggered

Without GitHub Actions, you’d do all of this manually. With it, you save time, reduce errors, and speed up delivery.

In DevOps, automation = power. GitHub Actions brings that power to your repos.

---

🔹 Building Blocks of GitHub Actions

GitHub Actions might sound complex, but it’s built on a few simple concepts:

1. Workflows 🛠

   • A workflow is an automation pipeline defined in YAML files inside .github/workflows/.

   • Example: Run tests every time code is pushed.

2. Events & Triggers ⚡

   • Workflows are triggered by events.

   • Example: A push event, a pull_request, or even a cron job (scheduled runs).

3. Jobs 📦

   • A workflow is made of one or more jobs.

   • Each job runs in its own runner (VM or container).

4. Steps 🧩

   • Each job has steps → commands or actions that execute.

   • Example: checkout code, install dependencies, run tests.

5. Actions 🎯

   • The building blocks inside steps.

   • You can use pre-built actions from the GitHub Marketplace or write your own.

---

🛠 Practical Exercise: Your First GitHub Action (Hello World)

We’ve learned the theory, now let’s get our hands dirty and build a Hello World GitHub Action.

But instead of pasting a huge YAML here, I’ve structured everything into a GitHub repo so you can follow day by day and actually run the workflows yourself 🎉.

👉 Repo: GitHub Actions Learning Journey

Inside the repo, you’ll find folders for each day and ready-to-run workflows under:

.github/workflows/day01-hello-world.yml

---

✅ Steps to Run Day 01 Workflow

1. Fork the repo

• Go to this repository

• Click Fork in the top-right corner.

  

2. Navigate to the Actions tab

• In your forked repo, click the Actions tab.

  

3. Select Day 01 Workflow

• From the left panel, choose Day 01 – Hello World.

  

4. Trigger the Workflow

• Click Run workflow → then select Run workflow again

5. View Results

• Once the workflow runs, open the logs.

  

• You’ll see Hello, GitHub Actions! 🎉 printed out.

---

🎯 Summary

• You now understand what GitHub Actions is.

• You learned about workflows, jobs, steps, and triggers.

• And you successfully ran your first GitHub Action workflow!

---

🌟 Follow My DevOps Learning Journeys

📌 Terraform Journey (30 Days) → [https://abdulraheem.hashnode.dev/series/terraform-with-aws]
📌 GitHub Actions Journey (Current) → [https://github.com/abdulraheem381/github-actions-journey]
📌 Daily Updates & Thoughts on X → [https://x.com/Abdulraheem183]

Let’s learn, build, and grow together 🚀