ENIGMA:Policy_for_master_branch - hpgDesigns/hpgdesigns-dev.io GitHub Wiki

In order to ensure that ENIGMA is not too unstable for neither users or developers, there is a simple policy to follow when making or accepting changes to the master branch of the ENIGMA code repository (https://github.com/enigma-dev/enigma-dev):

• Commits to the master branch should strive towards not breaking already working parts.
• Changes that are known to break working parts should not be committed to the master branch, unless the breaking are known and accepted by the other developers and contributors.
• Use forks or branches and inform others of the issues if you cannot fix or test the issues themselves, such that others can look at, test or fix them, before merging them into the master branch.