claude
fbec36cb67
Scaffold the course repo and author the full curriculum in dependency-chain order, following the settled build decisions in handoff.md. - Scaffold: course README, vendor-neutral AGENTS.md (dogfoods Module 5), _TEMPLATE.md (the fixed 9-section module shape), root .gitignore, ship config. - Modules 1-2: reference exemplars (locked for tone/depth/lab style). - Modules 3-27: full lessons + runnable labs, each following the template, respecting the chain, vendor/model-agnostic, with "feel the pain" labs. - Module 8 hosting comparison web-researched and date-stamped (as of 2026-06-22), not written from memory; expansion-zone modules carry Verify-before-publish. - Capstone: the full loop end to end on the running tasks-app example. Lab code syntax-checked (Python/shell/YAML); every module has the 7 core template sections. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TfzV5QvtPDz8LJS3Pu5VLT
47 lines
1.8 KiB
YAML
47 lines
1.8 KiB
YAML
# Starter CI workflow for the tasks-app — forge-native, GitHub Actions flavor.
|
|
#
|
|
# Where this file goes: GitHub Actions reads workflow files from the .github/workflows/ directory
|
|
# at the root of your repo. Copy this file to .github/workflows/ci.yml (the name "ci.yml" is yours
|
|
# to choose; the .github/workflows/ path is not). Commit it, push, and the forge runs it.
|
|
#
|
|
# The same three checks (lint, then test) exist on every forge — only the YAML shape differs. See
|
|
# gitlab-ci-starter.yml in this folder for the GitLab equivalent of this exact pipeline.
|
|
|
|
name: CI
|
|
|
|
# When should this run? "On every push, and on every pull request." That's the whole pitch of CI:
|
|
# nothing reaches the shared history without passing through here first.
|
|
on:
|
|
push:
|
|
pull_request:
|
|
|
|
jobs:
|
|
check:
|
|
# The runner: a fresh, throwaway Linux machine the forge spins up for this job. "Works on my
|
|
# machine" can't hide here — this machine has nothing of yours on it. (More on runners in
|
|
# Module 19, including running your own.)
|
|
runs-on: ubuntu-latest
|
|
|
|
steps:
|
|
# Step 1: get your code onto the runner. Without this the runner is empty.
|
|
- name: Check out the code
|
|
uses: actions/checkout@v4
|
|
|
|
# Step 2: install the language the project needs. Pin a version so CI matches what you run.
|
|
- name: Set up Python
|
|
uses: actions/setup-python@v5
|
|
with:
|
|
python-version: "3.12"
|
|
|
|
# Step 3: install the tools the checks need — the test runner and the linter from Module 13.
|
|
- name: Install tools
|
|
run: pip install pytest ruff
|
|
|
|
# Step 4: lint. Style and obvious-mistake check. Fails the job on any finding (non-zero exit).
|
|
- name: Lint
|
|
run: ruff check .
|
|
|
|
# Step 5: test. The Module 13 tests. A single failing assertion fails the whole job.
|
|
- name: Test
|
|
run: pytest -q
|