Skip to content

Latest commit

 

History

History
39 lines (25 loc) · 1.45 KB

CONTRIBUTING.md

File metadata and controls

39 lines (25 loc) · 1.45 KB

Contributing

How to

  1. Search existing issues to make sure you’re not submitting a duplicate.

  2. Open a new issue. Let’s discuss it before you start writing code.

  3. Grab the latest stable commit.

  4. Create a development branch according to this naming scheme:

    type/description

    Where type is one of:

    • feature
    • bug
    • chore

    And description is an all-lowercase, hyphen-separated description of what the branch is about.

    Examples:

    • feature/visa-support
    • bug/broken-mastercard-detection
    • chore/refactor-validate-function

    Be concise but descriptive.

  5. Commit your changes to the development branch.

  6. Make a pull request.

Releases

Stable

Latest stable version can always be found in the master branch.

You can find current and previous stable releases on the releases page.

Development

There are no development releases. All features, bugs and chores are developed in their own branches of master, then are merged into a release branch (eg release/1.1), which is in turn tagged and merged into master. Then the cycle repeats.