Commitizen

In order to maintain that process each commit message should follow a specificformatting. To ensure that formating, we use Commitizen which can be triggeredvia the following command. Additional information can be foundhere.

$ npm run commit

Then a set of questions will be presented to you:

$ npm run commit
cz-cli@2.4.6, cz-conventional-changelog@1.1.5
Line 1 will be cropped at 100 characters. All other lines will be wrapped
after 100 characters.
? Select the type of change that you're committing: (Use arrow keys)
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
(Move up and down to reveal more choices)
? Denote the scope of this change ($location, $browser, $compile, etc.):
ESLint
? Write a short, imperative tense description of the change:
Update code formatting to comply with our ESLint specification
? Provide a longer description of the change:
? List any breaking changes or issues closed by this change:

Code editing

Any code editor should be more than sufficient, however the recommended plugins listed below may not be as well supported or you may have to find alternative workarounds. The most important ones such as ES6/Babel syntax highlighting, ESLint are supported by multiple code editors which you may already use.

Otherwise, we highly recommend Sublime Text 3 with the following set of plugins.To install plugins you will have to first install Package control.