Skip to content

Latest commit

 

History

History
20 lines (15 loc) · 1.09 KB

CONTRIBUTING.md

File metadata and controls

20 lines (15 loc) · 1.09 KB

Contributing

  • Search on GitHub for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort.

  • Create the development environment as described in README.md.

  • Make your changes in a new git branch:

    git checkout -b my-branch master
  • Create your patch commit, including appropriate test cases.

  • Run the test tool and ensure that all unit tests and lint checks pass.

    tox
  • Commit your changes using a descriptive commit message that follows the AngularJS Commit Message Format. Adherence to the commit message conventions is required, because release versions and release notes are automatically generated from these messages.

  • After the review process for new features and bugfixes is done, please squash multiple commits to a single one. Single commits make it easier to revert later in case of problems.