World map

 

BM

World 7: Robots: Actions & CI/CD · Boss challenge

Auto-deploy the diary site

You will learn: to build, debug and trust a robot that deploys on every merge.

The problem

Practice repo — not a real website
aina-codes / diary
Add day 5 entry #12
Merged mei wants to merge day-5 into main
  1. mei

    Day 5: I learned GitHub Actions.

  2. You merged this (Squash and merge).

Day 5 is merged. But the live diary still shows day 4. You deploy by hand, and you forgot. Boss mission: every merge deploys by itself.

Watch

Tap each point on the timeline.

Here is the plan. Tap each stop. Then build it, debug it, and explain it. Kind hints help if you get stuck.

Try it

Room 1: build the robot. Deploy on every push to main, but only after the tests pass.

Tap blocks to add them. Put them in order.

Blocks

Your workflow

Tap a block above to start.

Workflow file .github/workflows/

name: Deploy diary

What runs

Nothing to run yet.

Try it

Room 2: the first real run is red! Find the step that failed.

Practice repo — not a real website
aina-codes / diary
Deploy diary #31
Failed push on main
Tap a step to see its log.
deploy

Check

Room 3: the tests failed, and the live site stayed safe. Why must deploy come after the tests?

You did it!

You can now auto-deploy a site, safely, on every merge.

Go deeper (optional)

This course deploys the same way. Its deploy job has needs: check and only runs on pushes to main. Make it real (optional). Turn on GitHub Pages for your diary repo. Set its source to GitHub Actions. Pick the static HTML starter workflow. Then check here.

Check it on GitHub

Your username is sent only to api.github.com.

  • A workflow ran in your diary repoNot checked yet
  • GitHub Pages is onNot checked yet