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