World map

 

BM

World T4: Modules & Pipelines

A plan on every pull request

You will learn: how a small workflow plans every change on the pull request, so the team reviews it first.

Checked with OpenTofu 1.13 on 1 Nov 2026

The problem

Ben ran tofu apply from his laptop. Nobody saw the plan. It destroyed the old menu board. How could the team have caught it in time?

Watch

Practice repo — not a real website
kedai-kancil / blueprint
Add a roti kiosk #8
Open ben wants to merge roti-kiosk into main
  1. ben

    One more kiosk from the kiosk module.

  2. plan-bot

    Plan for this pull request:

    # module.roti.local_file.sign will be created
Plan: 1 to add, 0 to change, 0 to destroy.
Checks
  • Passed tofu fmt
  • Passed tofu validate
  • Passed tofu plan
How to merge
Merging is blocked
  • This branch needs one approving review first.
Your review

Read the plan in the comment. Nothing to destroy? Then approve it.

Try it

Build the workflow that made those checks. Plan only: no apply here.

Tap blocks to add them. Put them in order.

Blocks

Your workflow

Tap a block above to start.

Workflow file .github/workflows/

name: Plan

What runs

Nothing to run yet.

Predict

Ben forgot to run tofu fmt. His pull request runs this workflow. What happens?

Check

Where does each step belong?

Drag a card into a box. Or tap the card, then tap the box.

      Check

      Swipe: a good pipeline habit, or needs work?

      Swipe right for good, left for needs work. Or use the buttons.

      1 / 4

      Plan on every pull request, apply after merge with an approval

      You did it!

      You can now plan every change on a pull request, for the team to review.

      Go deeper (optional)

      In CI the plan needs the shared backend (T3·1). Without it, the register looks empty. Posting the plan as a comment needs pull-requests: write and a small script. For apply after merge, save the plan with -out and apply exactly that file. Atlantis or HCP Terraform can run this loop for you. Mission 8 puts this workflow on your repo.