mikkeli/handbooks
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add repo-naming rule (hyphens, not underscores)

Browse Source 
New repos only, same non-retroactive caveat as trunk naming.
Underscores don't survive the trip to a domain, a Docker tag, or
most package-registry names, where hyphens do; matches the
kebab-case already used for branch descriptions.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011EBCcjJvEvhpToahqdsLLA
This commit is contained in:
Mikkeli Matlock
2026-08-22 21:47:17 +09:00
parent 2e5f6b4db0
commit 54d6aebbe5
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
git-operations.md
+3
View File
@@ -28,6 +28,9 @@ deviation from this default, and belongs in that project's own KB corpus, not he
else), work with what's there. Never rename a repo's default branch as an incidental part of else), work with what's there. Never rename a repo's default branch as an incidental part of
unrelated work. unrelated work.
**Repo name: hyphens, not underscores** (`my-project`, not `my_project`) — for new repos, same
caveat as trunk naming: don't rename an existing one over this.
**Naming scheme: `type/short-description`.** A type prefix from the taxonomy below, then a **Naming scheme: `type/short-description`.** A type prefix from the taxonomy below, then a
kebab-case description — `feat/branch-naming-rules`, `fix/null-check-on-login`. No ticket ID in the kebab-case description — `feat/branch-naming-rules`, `fix/null-check-on-login`. No ticket ID in the
name: a branch name should say what the change does, and if a tracker ticket exists, that reference name: a branch name should say what the change does, and if a tracker ticket exists, that reference