groombook/org
13
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(skills): remove stale no-self-merge contract refs (GRO-2763) #18

Merged
Flea Flicker merged 1 commits from pe/GRO-2763-remove-no-self-merge-contract-refs into main 2026-08-23 08:30:36 +00:00
Conversation 0 Commits 1 Files Changed 3
+3 -3
3 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/coding-standards/SKILL.md
+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.
---
skills/devops/SKILL.md
+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
skills/sdlc/SKILL.md
+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"