From 54d6aebbe556e4b346a55b7b9732abeb42fe6e05 Mon Sep 17 00:00:00 2001 From: Mikkeli Date: Sat, 22 Aug 2026 21:47:17 +0900 Subject: [PATCH] docs: add repo-naming rule (hyphens, not underscores) 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 Claude-Session: https://claude.ai/code/session_011EBCcjJvEvhpToahqdsLLA --- git-operations.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/git-operations.md b/git-operations.md index e8fc182..d74d3f6 100644 --- a/git-operations.md +++ b/git-operations.md @@ -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 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 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