2 Commits

Author SHA1 Message Date
Flea Flicker d6d94623f4 docs(skills): remove stale no-self-merge contract refs (GRO-2763)
Remove stale no-self-merge contract references left by org#17 (GRO-2377 fast-follow). Fixes coding-standards, sdlc, and devops skills.
2026-08-23 08:30:35 +00:00
Scrubs McBarkley d3f7a91e53 docs(devops): fix-forward-in-git rule — ban escalating reconcilable changes as manual/board actions (GRO-2536)
Adds "fix forward in git" rule to devops skill: any breakage a controller (Flux/OpenTofu/SealedSecrets) can reconcile must be resolved via PR to groombook/infra — not board approval, not hand-run kubectl. Prevents recurrence of GRO-2536 stall.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
Co-authored-by: Scrubs McBarkley <18+gb_scrubs@noreply.git.farh.net>
Co-committed-by: Scrubs McBarkley <18+gb_scrubs@noreply.git.farh.net>
2026-06-25 12:35:07 +00:00
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -4,7 +4,7 @@ description: >
Engineering quality bar for GroomBook code: priority ordering of correctness
vs. clarity vs. maintainability vs. performance vs. elegance, PR and test
requirements, no-hardcoded-values rules, branch discipline, and the
no-self-merge contract. The uat→main merge-gate policy lives in the `sdlc`
PR self-merge rule. The uat→main merge-gate policy lives in the `sdlc`
skill, not here.
---
+1 -1
View File
@@ -35,7 +35,7 @@ Use the `GITEA_TOKEN` environment variable for all Gitea operations — it is al
tea pr create --base main --title "..." --body "... cc @cpfarhood"
```
Gitea branch protection requires CI checks to pass. See `coding-standards` for the no-self-merge contract and the `cc @cpfarhood` rule.
Gitea branch protection requires CI checks to pass. See `coding-standards` for the PR self-merge rule and the `cc @cpfarhood` rule.
## Infrastructure topology
+1 -1
View File
@@ -36,7 +36,7 @@ Three long-lived branches map to the three deployment environments:
## Pull requests
All changes happen via pull request. Gitea branch protection requires CI checks to pass. See `coding-standards` for the no-self-merge contract and the `cc @cpfarhood` visibility rule.
All changes happen via pull request. Gitea branch protection requires CI checks to pass. See `coding-standards` for the PR self-merge rule and the `cc @cpfarhood` visibility rule.
```bash
tea pr create --base dev --title "..." --body "... cc @cpfarhood"