DevOps feedback & continuous integration

Make a small change easy to review

Lesson 1 of 20 · 9 min · Module 1: Feedback and workflow structure

A delivery workflow should give a team quick, repeatable evidence about a change.

Start this lesson →

Free. No installation: you write and run the code in your browser, and it is checked automatically.

By the end, you’ll be able to…

  • Connect a change to feedback
  • Choose events that represent team work

The idea

A workflow combines an event boundary, job dependencies, and ordered steps. Conditions and prerequisite outcomes determine which jobs can run.

name: Example feedback
on: pull_request
jobs:
  inspect:
    runs-on: ubuntu-latest
    steps:
      - run: echo Review this change

01Connect a change to feedback

A small focused change is easier to review and recover than a large batch. CI runs repeatable checks so teammates can discuss evidence rather than rely on one developer machine.

02Choose events that represent team work

Pull requests provide a useful premerge boundary. A main-branch push can verify the merged result. The workflow should express both intentionally.

03Keep responsibility shared

Automation supports collaboration; it does not replace review, ownership, or an explanation of a failed check. This lab simulates jobs and never edits a real repository.

Your turn

Create a workflow triggered by push to main and pull_request. Add a test job on ubuntu-latest that runs npm test. Keep contents permission read-only.

What the checks look for

  • Checks pull requests and main pushes
  • Runs the test job with read-only contents
Try it in the editor →

Take this with you

Design a fast feedback loop around small, reviewable changes.

Go a little further

Write a short pull request description explaining the evidence a reviewer should inspect.

Learn CI/CD & Release Engineering for free

20 short lessons with real code and instant checks.

See the whole course →