-
Notifications
You must be signed in to change notification settings - Fork 2
Issues and Pull Requests
Sara Reffler edited this page Feb 7, 2025
·
2 revisions
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 |
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. |