Skip to content

Latest commit

 

History

History
32 lines (23 loc) · 1.04 KB

File metadata and controls

32 lines (23 loc) · 1.04 KB

CONTRIBUTING

Git commit message format

This section reproduced from this blog

<type>(<scope>): <subject>

"type"

build: Build related changes (eg: npm related/ adding external dependencies) chore: A code change that external user won't see (eg: change to .gitignore file or .prettierrc file) feat: A new feature fix: A bug fix docs: Documentation related changes refactor: A code that neither fix bug nor adds a feature. (eg: You can use this when there is semantic changes like renaming a variable/ function name) perf: A code that improves performance style: A code that is related to styling test: Adding new test or making changes to existing test

"scope" is optional

Scope must be noun and it represents the section of the section of the codebase Refer this link for example related to scope

"subject"

use imperative, present tense (eg: use "add" instead of "added" or "adds") don't use dot(.) at end don't capitalize first letter