docs(git): sharpen text-change example, add prose-vs-bullets rule

This commit is contained in:
moilanik 2026-03-17 12:25:38 +02:00
parent a581c4ea98
commit b51a05e203

View File

@ -100,9 +100,9 @@ Types: `feat`, `fix`, `docs`, `refactor`, `chore`
- ✅ `disable redis sub-chart`
- ✅ `set queue type to level`
- Do not summarize or quote the content of text/description changes — the diff shows the content, the message states that the change happened
- ❌ `Remove technical cleanup instructions — not accessible to users. Replace with operational guidance: spikes are normal, daily return to 0 is expected, notify developer if count stays elevated.`
- ✅ `update Ghost Blocks panel description`
- ❌ `Remove "harmless" framing, add operational guidance: daily return to 0 expected`
- ✅ `update Ghost Blocks panel description to reflect operational expectations`
- Body format: use prose (one sentence) for a single change; use bullets when there are multiple distinct changes
**Body length example — what "too much explanation" looks like vs. the correct version:**