Your First GitHub Workflow
Create and execute your very first GitHub Actions workflow to automate a simple task in your repository.
Your First GitHub Workflow is a free DevOps Bootcamp lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the DevOps Bootcamp learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Welcome to Workflows!
A workflow is an automated recipe of steps that runs in your repo. You write it as YAML and drop it into .github/workflows/.
The Core: Name & Triggers
Every workflow needs a name to identify it and an on key for its trigger. Use on: push to run whenever code lands.
Jobs: The Units of Work
Once you’ve set when a workflow runs, jobs defines what it does. Each job is an independent unit of work with its own id.
Runners: Your Virtual Machine
The runs-on key picks the machine for your job. ubuntu-latest is the go-to; windows-latest and macos-latest are there when you need them.
Steps: The Action Sequence
Inside a job, steps run in order. run executes a shell command; uses pulls in a prebuilt action. We’ll start with run.
Your First Workflow: Hello!
Here’s a complete starter workflow: it checks out your code, prints a greeting, and lists files. Save it as hello-workflow.yml and run it.
name: My First Hello Workflow
on: [push]
jobs:
say_hello_job:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Say Hello World
run: echo "Hello from GitHub Actions!"
- name: List current directory files
run: ls -laUnderstanding the `run` Command
The run key executes any shell command on the runner — echo to print, ls -la to list files. Chain many lines with |.
Triggering Your Workflow
With on: [push], your workflow fires automatically once you commit and push the YAML file to your repo. No manual trigger needed.
Viewing Workflow Runs
Head to the Actions tab in your repo to watch runs live — status, jobs, steps, and full logs for debugging any failure.
Quick Check: Workflow Structure
Which of the following is NOT a top-level keyword used directly in a basic GitHub Actions workflow YAML file?
Recap: Your First Automation!
You built and triggered your first workflow: it lives in .github/workflows/, starts on an event, and runs steps on a chosen runner. Nice.
Frequently asked questions
Is the “Your First GitHub Workflow” lesson free?
Yes — the full text of “Your First GitHub Workflow” is free to read here on the web, and the DevOps Bootcamp course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the DevOps Bootcamp course, upgrade to CoddyKit PRO.
What will I learn in “Your First GitHub Workflow”?
Create and execute your very first GitHub Actions workflow to automate a simple task in your repository. You practise DevOps Bootcamp with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start DevOps Bootcamp?
No prior experience is required. DevOps Bootcamp on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Your First GitHub Workflow” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this DevOps Bootcamp lesson?
Yes. Every DevOps Bootcamp lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- What is CI/CD and DevOps?
- GitHub Actions Core Concepts
- Your First GitHub Workflow
- Managing Secrets and Environment Variables