| name | ci-cd |
| description | How to set up and maintain CI/CD per stack. GitHub Actions patterns, testing configurations, deployment scripts. |
Setting Up CI for a New Project
When Builder completes a new project, Operator sets up CI. Standard checklist:
- Identify the stack (Python, TypeScript, Rust, etc.)
- Create
.github/workflows/ci.yml with the appropriate test runner
- Verify the workflow triggers on
push to main and on pull requests
- Confirm the test command matches the project's actual test runner
GitHub Actions Patterns by Stack
Python
- uses: actions/setup-python@v4
with: { python-version: "3.11" }
- run: pip install -e ".[dev]"
- run: pytest
Node / TypeScript
- uses: actions/setup-node@v4
with: { node-version: "20" }
- run: npm ci
- run: npm test
Maintaining Existing CI
On each heartbeat: check main branch CI (gh run list --branch main), action version
pins, and test command accuracy. A failing main branch is the highest priority —
address before any other operational work.
Deployment
Deployment scripts live in projects/{project-name}/.factory/deploy.sh or as a
GitHub Actions workflow. Do not invoke deployments without explicit human authorization.
Confirm target environment, authentication method, and rollback procedure before writing.
