Skip to content

Issues and Pull Requests

Sara Reffler edited this page Feb 7, 2025 · 2 revisions

Commit Types

Use the below table to prefix the titles of your PR and Issues. These align to the commit types standardized by Azure and Conventional Commits and improve both semantic understanding and integration with automation tools.

Commit Type Prefix Title Description
feat ✨ Feat Features A new feature
fix πŸ› Fix Bug Fixes A bug Fix
docs πŸ“š Docs Documentation Documentation only changes
styles πŸ’Ž Styles Styles Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
refactor πŸ“¦ Refactor Code Refactoring A code change that neither fixes a bug nor adds a feature
perf πŸš€ Perf Performance Improvements A code change that improves performance
test 🚨 Test Tests Adding missing tests or correcting existing tests
build πŸ›  Build Builds Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
chore ♻️ Chore Chores Other changes that don't modify src or test files
revert πŸ—‘ Revert Reversion Reverts a previous commit

Alternate prefixes

For non-dev tasks, use any of the following:

Prefix Title Description
🧠 Brainstorm Research & Brainstorm Non-development tasks, completed outside of Git
🎨 Design Design UX and UI tasks, completed in Figma
πŸ“‹ Review Review Peer review, mentor review, end of Sprint review, etc.

Clone this wiki locally