git-branch-format

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Generates a branch name from a description of changes.

根据变更描述生成分支名称。

{type}/{TICKET_NUMBER}_{short_description}

{type}/{TICKET_NUMBER}_{short_description}

{type}/{short_description}

Never use placeholders like

NO-TICKET

. If there's no ticket, just omit that part entirely.

{type}/{short_description}

切勿使用

NO-TICKET

这类占位符。如果没有工单编号，直接省略该部分即可。

Type	When to use
`feat`	New functionality
`fix`	Bug fix
`refactor`	Code change with no behavior change
`chore`	Config, deps, tooling, maintenance
`test`	Adding or updating tests
`docs`	Documentation only
`style`	Formatting, whitespace
`perf`	Performance improvement
`ci`	CI/CD changes
`build`	Build system changes
`revert`	Reverting a previous commit

Read the user's description of changes.
Ask: "Do you have a ticket number for this?" — if the user doesn't provide one, proceed without it.
Infer the correct
```
type
```
from the nature of the changes.
Generate the branch name following the convention above.

User: "I'm adding dark mode support" — Ticket: PROJ-312

feat/PROJ-312_dark_mode_support

User: "fixing a crash on the payment screen" — No ticket

fix/payment_screen_crash

User: "upgrading Flutter and fixing deprecated APIs" — Ticket: PROJ-548

feat/PROJ-548_flutter_upgrade

用户：“我要添加深色模式支持”——工单编号：PROJ-312

feat/PROJ-312_dark_mode_support

用户：“修复支付页面的崩溃问题”——无工单编号

fix/payment_screen_crash

用户：“升级Flutter并修复已废弃的API”——工单编号：PROJ-548

feat/PROJ-548_flutter_upgrade