- Make sure there's an existing issue in the project for the work you're about to start. The issue should be focused on just one thing.
- After forking the repo, create a branch named
feature/issuenumber-shortdesc
orbugfix/issuenumber-shortdesc
. - Keep commits small-ish, commit messages should reference the ticket number, for example with hash symbol, for example
[#17] Description of what was changed
. - Maintain or add new tests as needed. Test files are located in the same folder as the source. For example, file
lib/calc-util.js
has correspondinglib/calc-util.test.js
.