Fix MD029 ordered list numbering in SDLC.md and SDLC-example.md
Restart numbering at 1 for each sub-section's ordered list to satisfy markdownlint MD029 (ol-prefix) rule. Co-Authored-By: Paperclip <noreply@paperclip.ing>
This commit is contained in:
+6
-6
@@ -63,15 +63,15 @@ Prod stage: CEO merges uat→main PR → [auto deploy Production]
|
||||
|
||||
### UAT Stage
|
||||
|
||||
4. CTO opens a PR from `dev` → `uat` to promote the change, assigns Shedward Scissorhands for regression: `status: "todo"`
|
||||
5. Shedward runs UAT. Pass → reports to CTO. Fail → reports to CTO (CTO cascades to engineer).
|
||||
6. CTO assigns Barkley Trimsworth for security review: `status: "todo"`
|
||||
7. Barkley reviews. Pass → CTO assigns to CEO. Fail → CTO cascades to engineer.
|
||||
1. CTO opens a PR from `dev` → `uat` to promote the change, assigns Shedward Scissorhands for regression: `status: "todo"`
|
||||
2. Shedward runs UAT. Pass → reports to CTO. Fail → reports to CTO (CTO cascades to engineer).
|
||||
3. CTO assigns Barkley Trimsworth for security review: `status: "todo"`
|
||||
4. Barkley reviews. Pass → CTO assigns to CEO. Fail → CTO cascades to engineer.
|
||||
|
||||
### Prod Stage
|
||||
|
||||
8. CEO reviews and merges the `uat` → `main` PR → auto-deploy to Production.
|
||||
9. CEO rejects → returns to CTO → engineer.
|
||||
1. CEO reviews and merges the `uat` → `main` PR → auto-deploy to Production.
|
||||
2. CEO rejects → returns to CTO → engineer.
|
||||
|
||||
### Hierarchy Rules
|
||||
|
||||
|
||||
@@ -56,26 +56,26 @@ Merge: Countess von Containerheim merges after all approvals
|
||||
|
||||
### Stage 2 — UAT Review
|
||||
|
||||
4. Pixel Patty picks up PRs with passing CI.
|
||||
5. Patty runs E2E browser testing against the deployed build in `privilegedescalation-dev`.
|
||||
6. Pass → hands off to QA. Fail → reports back; CTO cascades to engineer.
|
||||
1. Pixel Patty picks up PRs with passing CI.
|
||||
2. Patty runs E2E browser testing against the deployed build in `privilegedescalation-dev`.
|
||||
3. Pass → hands off to QA. Fail → reports back; CTO cascades to engineer.
|
||||
|
||||
### Stage 3 — QA Review
|
||||
|
||||
7. Regression Regina picks up PRs that have passed both CI and UAT.
|
||||
8. Regina reviews: test coverage, regressions, edge cases, code quality.
|
||||
9. Pass → hands off to CTO. Fail → reports back; CTO cascades to engineer.
|
||||
1. Regression Regina picks up PRs that have passed both CI and UAT.
|
||||
2. Regina reviews: test coverage, regressions, edge cases, code quality.
|
||||
3. Pass → hands off to CTO. Fail → reports back; CTO cascades to engineer.
|
||||
|
||||
### Stage 4 — CTO Review
|
||||
|
||||
10. Null Pointer Nancy picks up PRs that have passed CI, UAT, and QA.
|
||||
11. Nancy reviews: architecture alignment, code quality, security.
|
||||
12. Approve → PR is ready for merge. Request changes → cascades to engineer.
|
||||
1. Null Pointer Nancy picks up PRs that have passed CI, UAT, and QA.
|
||||
2. Nancy reviews: architecture alignment, code quality, security.
|
||||
3. Approve → PR is ready for merge. Request changes → cascades to engineer.
|
||||
|
||||
### Stage 5 — CEO Merge
|
||||
|
||||
13. Countess von Containerheim merges the PR after all three approvals (UAT + QA + CTO) and CI passing.
|
||||
14. Reject → returns to CTO → engineer.
|
||||
1. Countess von Containerheim merges the PR after all three approvals (UAT + QA + CTO) and CI passing.
|
||||
2. Reject → returns to CTO → engineer.
|
||||
|
||||
### Hierarchy Rules
|
||||
|
||||
|
||||
Reference in New Issue
Block a user