sdaduanbilei/cc-haha
1
0
Fork 0
mirror of https://github.com/NanmiCoder/cc-haha synced 2026-07-19 13:33:35 +08:00
Code Issues Packages Projects Releases Wiki Activity

Document repository branch naming policy

Browse Source 
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:
程序员阿江(Relakkes) 2026-04-27 20:33:25 +08:00
parent 664c6ebd9f
commit 438c9efbbc
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
AGENTS.md
View File

@ -34,3 +34,4 @@ Desktop tests use Vitest with Testing Library in a `jsdom` environment. Name tes
## Commit & Pull Request Guidelines ## 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. 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.