From 438c9efbbc67a9fcc863c6fb696e1feb277fe708 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E7=A8=8B=E5=BA=8F=E5=91=98=E9=98=BF=E6=B1=9F=28Relakkes?= =?UTF-8?q?=29?= Date: Mon, 27 Apr 2026 20:33:25 +0800 Subject: [PATCH] Document repository branch naming policy The repository uses product-oriented branch prefixes rather than Codex-specific names, so the workspace guidance now records that convention for future local branch creation. Constraint: Repository guidance should stay compact and only capture durable workflow rules. Confidence: high Scope-risk: narrow Tested: not run; documentation-only change --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index fbce778b..a6426894 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -34,3 +34,4 @@ Desktop tests use Vitest with Testing Library in a `jsdom` environment. Name tes ## Commit & Pull Request Guidelines Recent history follows Conventional Commit prefixes such as `feat:`, `fix:`, and `docs:`. Keep subjects imperative and scoped to one change. PRs should explain the user-visible impact, list verification steps, link related issues, and include screenshots for desktop or docs UI changes. Keep diffs reviewable and call out any follow-up work or known gaps. +Branch names should use normal product prefixes such as `fix/xxx`, `feat/xxx`, or `docs/xxx`; do not create `codex/`-prefixed branches in this repository.