Skip to content

Commit 8a87e84

Browse files
anobakaclaude
andcommitted
docs(claude): warn about literal skip-ci substrings in commit bodies
GitHub matches the directive anywhere in the message, so prose that mentions it (e.g. explaining a manual-override path) will silently skip the pipeline. Just bit us on 0a428be. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent 0a428be commit 8a87e84

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

‎.claude/CLAUDE.md‎

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -143,6 +143,14 @@ docs: 更新 GitHub issue 管理工作流程 [skip ci]
143143
Closes #123
144144
```
145145

146+
**Trap**: GitHub matches the skip tokens (`[skip ci]`, `[ci skip]`,
147+
`[no ci]`, `[skip actions]`, `[actions skip]`) as literal substrings
148+
*anywhere* in the commit message — subject **or** body. So when a
149+
commit's body *describes* the directive (e.g. explaining a workflow's
150+
manual-override path), don't write the literal token inline, or that
151+
commit itself will skip the pipeline. Reword it (`the skip-ci
152+
directive`, `[ skip ci ]` with spaces, etc.) instead.
153+
146154
## 自动化 Issue 处理规范
147155

148156
当被要求处理 GitHub Issue 时,你必须严格遵循以下 4 步流程:

0 commit comments

Comments
 (0)