You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From v2 onwards, we will be using conventional commits. This will help with generating changelogs etc. Additionally, all work will be done on the v2 trunk using feature branches and they will be rebase-merged in all cases, effectively removing any and all merge commits from the trunk. We shall adhere to this convention for all future changes, too.
Commit types
Commit Type
Title
Description
Emoji
feat
Features
A new feature
✨
fix
Bug Fixes
A bug Fix
🐛
docs
Documentation
Documentation only changes
📚
style
Styles
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
💎
refactor
Code Refactoring
A code change that neither fixes a bug nor adds a feature
📦
perf
Performance Improvements
A code change that improves performance
🚀
test
Tests
Adding missing tests or correcting existing tests
🚨
build
Builds
Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
🛠
ci
Continuous Integrations
Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
From v2 onwards, we will be using conventional commits. This will help with generating changelogs etc. Additionally, all work will be done on the
v2
trunk using feature branches and they will be rebase-merged in all cases, effectively removing any and all merge commits from the trunk. We shall adhere to this convention for all future changes, too.Commit types
feat
fix
docs
style
refactor
perf
test
build
ci
chore
revert
Source
The text was updated successfully, but these errors were encountered: