DevOps Playbook

Jump to bottom

Weixian edited this page May 28, 2026 · 5 revisions

Naming Conventions

Commit Message

we follow semantic commit messages examples:

feat: add shopping cart checkout
fix: resolve null pointer in user service
refactor: simplify inventory validation
docs: update setup instructions
test: add unit tests for auth module
chore: upgrade npm dependencies

Branch name

Issue Title

Pull request Title

Standards

1 PR = 1 feature or bug fix
Commit and sync remote at least once a day or multiple times per day
always label issue: feature, bugfix, frontend, backend, module-name and etc
Always create release note for every production release (BA help on this)