BigPapiCB CI/CD
Decision Tree
Need CI/CD → What stack?
├─ Node/TypeScript → Use assets/ci-node.yml.template
├─ Python → Use assets/ci-python.yml.template
└─ Multi-stack → Combine relevant templates
Pipeline Stages
Push/PR → Lint → Test → Build → Deploy (main only)
Key Patterns
Caching
- uses: actions/cache@v4
with:
path: ~/.npm
key: npm-${{ hashFiles('**/package-lock.json') }}
restore-keys: npm-
Branch Protection
- Require PR reviews before merge
- Require status checks to pass
- Require branch is up to date
- No force pushes to main
Secrets
- Use GitHub Secrets (never echo in logs)
- Use OIDC for cloud deployments (no static credentials)
- Scope secrets to environments (staging, production)
Anti-Patterns
| Anti-Pattern | Fix |
|---|---|
| No caching | Cache dependencies |
npm install in CI |
Use npm ci (deterministic) |
| Skip tests for speed | Parallelize instead |
| Deploy on every push | Use tags/releases |
| Manual version bumps | Automate with semantic-release |
Templates:
- Node/TypeScript CI
- Python CI