This lab removes the need to hunt for a random public workflow. Run it in your disposable git-github-lab repository.
Copy these files into your student lab:
examples/actions/demo/app.py→app.pyexamples/actions/demo/tests/test_app.py→tests/test_app.pyexamples/actions/basic-python-ci.yml→.github/workflows/ci.yml
Commit and push them.
Open .github/workflows/ci.yml and identify:
- the events under
on - the job under
jobs - the runner
- each step
- the command that decides whether the check passes
Open the Actions tab or the commit checks. Confirm the tests pass.
In tests/test_app.py, change the expected result for add(2, 3) from 5 to 6, commit, and push.
Predict the result before checking GitHub.
Confirm the workflow fails and inspect the failing test output.
Restore the correct expectation, commit, push, and verify the workflow returns to green.
You can explain why CI is useful, what caused the red check, and why a green check only proves the checks that actually ran—not all possible correctness.