Contributing Guide
Commit Message Guidelines
Multiwoven follows the following format for all commit messages.
Format: <type>([<edition>]) : <subject>
Example
feat(CE): add source/snowflake connector
^--^ ^--^ ^------------^
| | |
| | +-> Summary in present tense.
| |
| +-------> Edition: CE for Community Edition or EE for Enterprise Edition.
|
+-------------> Type: chore, docs, feat, fix, refactor, style, or test.
Supported Types:
feat
: (new feature for the user, not a new feature for build script)fix
: (bug fix for the user, not a fix to a build script)docs
: (changes to the documentation)style
: (formatting, missing semi colons, etc; no production code change)refactor
: (refactoring production code, eg. renaming a variable)test
: (adding missing tests, refactoring tests; no production code change)chore
: (updating grunt tasks etc; no production code change)
Sample messages:
- feat(CE): add source/snowflake connector
- feat(EE): add google sso
References:
Was this page helpful?