Note: This styleguide is not an exhaustive list of rules and processes. It is rather an emerging repository of habits that have proven to be something called "good software engineering practices". This repository can be modified at any time without any prior notification, if you want to stay on top of it please hit the star and follow updates.
The aim of this styleguide is to:
- inform guests on processes within Bleenco development team,
- brief new candidates and encourage them to submit their first pull request,
- remind current contributors what quality standard do we stand for.
To ensure consistency throughout the source code, keep these rules in mind as you are working:
- All features or bug fixes must be tested by one or more specs (unit-tests, API tests).
- All public API methods must be documented.
- Abstruse build must be green