GitHub Actions
Automation on every push.
GitHub Actions runs tasks for you, automatically, whenever something happens in your repository. Like running tests on every push, or checking every pull request before it's merged.

- Automatic tasks
- Triggered by pushes and pull requests
- Tests, checks, deploys
Key words
A few words to know. A workflow is a file describing the automation. An event is what triggers it, like a push. A job is a group of steps that runs on a fresh virtual machine, called a runner. And steps are the individual commands.
Your first workflow
Workflows live in a folder called dot github slash workflows. This one is named check site. It runs on every push to main, and on every pull request. It has one job, called check, on an ubuntu machine. The first step checks out our code. The second step runs a small script, check dot SH, that fails if any page is missing a heading.
name: Check site
on:
push:
branches: [main]
pull_request:
jobs:
check:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Check every page has a title
run: sh check.shSummary
GitHub Actions runs workflows, written in YAML, on events like push and pull request. Next, seeing the results.
Key takeaways- .github/workflows/*.yml
- on: push, pull_request
- jobs and steps