Add two-pipeline routing to SDLC skill

Document Pipeline A (user-facing, full UAT→QA→CTO) and Pipeline B
(infrastructure-only, skip UAT, QA→CTO) based on changed file types.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
2026-05-08 16:55:05 +00:00
committed by Null Pointer Nancy [agent]
parent 12ccf82454
commit 88e0f7ddf9
+13
View File
@@ -140,6 +140,19 @@ Merge: Countess von Containerheim merges after all approvals
13. Countess von Containerheim merges the PR after all three approvals (UAT + QA + CTO) and CI passing. 13. Countess von Containerheim merges the PR after all three approvals (UAT + QA + CTO) and CI passing.
14. Reject → returns to CTO → engineer. 14. Reject → returns to CTO → engineer.
### Pipeline Routing
PRs are classified into two pipelines based on changed files:
| Pipeline | Trigger | Stages |
|----------|---------|--------|
| **A — User-facing** | PR changes any plugin runtime files (`src/`, `package.json`, `pnpm-lock.yaml`, `tsconfig.json`, `artifacthub-pkg.yml`) | CI → UAT → QA → CTO → CEO merge |
| **B — Infrastructure** | PR changes ONLY infrastructure files (`.github/`, `*.md`, `.eslintrc*`, `.prettierrc*`, `renovate.json*`, `.gitignore`, `.editorconfig`, `LICENSE`) | CI → QA → CTO → CEO merge (skip UAT) |
**Default is Pipeline A** — if any changed file does not match the infrastructure-only list, the full pipeline applies.
Pipeline B requires **2 approving GitHub reviews** (QA + CTO) instead of 3. The `dual-approval-check` workflow enforces this gate.
### Hierarchy Rules ### Hierarchy Rules
- CTO rejections go directly to engineer (not through QA or UAT). - CTO rejections go directly to engineer (not through QA or UAT).