Skip to content

Latest commit

 

History

History
53 lines (33 loc) · 1.51 KB

CONTRIBUTING.md

File metadata and controls

53 lines (33 loc) · 1.51 KB
Raw

Contributing

I am open to any contributions made by you.

Linting

Please check your code using npm run lint before submitting your pull requests.

Some .cssnext.js files will display an error. This is normal because we use sass as default extension language.

Testing

Please check your code using npm run test before submitting your pull requests.

Commit Message Format

Each commit message should include a type, a scope and a subject:

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

Any line of the commit message cannot be longer 100 characters! This allows the message to be easier to read on GitHub as well as in various git tools.

Type

Must be one of the following:

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
  • refactor: A code change that neither fixes a bug or adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests
  • chore: Changes to the build process or auxiliary tools and libraries such as documentation generation

Scope

The scope could be anything specifying place of the commit change. For example webpack, server, eslint, babel, reactComponentName etc...

Subject

The subject contains succinct description of the change:

  • use the imperative, present tense: "change" not "changed" nor "changes"
  • don't capitalize first letter
  • no dot (.) at the end