mirror of
https://github.com/NanmiCoder/cc-haha
synced 2026-07-15 12:53:31 +08:00
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
This commit is contained in:
parent
664c6ebd9f
commit
438c9efbbc
@ -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.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user