Portfolio

Case study

Rendered from the project README. Workflows run on the public caoyadong888-wq/pipeforge-demo repository. Kestrel Parcel Co. is fictional, not a client. Nothing is deployed to a server from this pipeline.

PipeForge (portfolio harness)

Stage B: live public demo repository on caoyadong888-wq/pipeforge-demo. The application and workflows live in /workspace/pipeforge-demo. This directory records runs, snapshots workflows, and builds the static showcase under site/pipeforge/.

Locked decisions

  1. Owner: caoyadong888-wq (existing account). Isolation via a separate

public repo. repo.env sets GH_OWNER.

  1. Public README does not link back to the portfolio host.
  2. GHCR package is public.
  3. One demo PR and one intentionally scan-blocked PR.
  4. main requires CI status checks; reviews not required.

Commands

make tools      # install actionlint / shellcheck
      make check      # offline lint, zizmor, app tests, policy tests
      make record     # pull live runs/badges/snapshots from GitHub
      make showcase   # record + rebuild site/pipeforge/
      make test       # pytest for harness tests

No deploy and no VPS steps from this tree.

Open the live demo