Skip to main content

PR with Conventional Commit prefix

  • ✨ feat: clear, user-facing changes.
  • 🩹 fix: bug fixes.
  • ♻️ refactor: internal code improvements, no behavior change.
  • 👷 build: build system & pipelines.
  • ⚡️ perf: explicit for performance optimizations.
  • ✅ test: add testcases.
  • 📝 docs: documentation updates.
  • 🔨 chore: catch-all for maintenance, dependencies, configs, formatting.

Issue type/label

  • 🐛 bug — broken functionality
  • ✨ request — new functionality
  • 🍄 improvement — kaizen / polish / performance / DX
  • 🔍 testing — add/fix tests
  • 🏗 refactor — internal restructuring
  • 🎨 design — UI/UX work
  • 🔒 security — vulnerabilities / hardening
  • 🔬 research — spikes, POCs
  • 🗃 documentation — documentation
  • 💬 discussion — proposals / decisions
  • 🔹 size: S
  • 🔶 size: M
  • 🔴 size: L
  • 👺 size: XL
  • 🤔 Need Reproduce
  • 🕗 Todo
  • 🧑‍💻 Doing
  • 🚽 WON'T DO
  • 📦 Released
🗎 Refs:
https://github.com/lobehub/lobe-chat-agents/tree/main/.github
https://www.conventionalcommits.org/en/v1.0.0/#summary
https://conventional-branch.github.io/
https://graphite.dev/guides/git-branch-naming-conventions
https://medium.com/@abhay.pixolo/naming-conventions-for-git-branches
https://dev.to/varbsan/a-simplified-convention-for-naming-branches-and-commits