Contributions to the Inchoo Payway codebase are done using the fork/branch & pull model.
The development team will review all issues and contributions submitted by in the first in, first out order. During the review, additional clarifications from the contributor may be required.
- Contributions must adhere to Magento coding standards.
- Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Comprehensive descriptions increase the chances of a pull request to be merged quickly and without additional clarification requests.
- Commits must be accompanied by meaningful commit messages.
- PRs which include bug fixing, must be accompanied with step-by-step description of how to reproduce the bug, or reference existing Issue.
- Search current listed issues (open or closed) for similar proposals of intended contribution before starting work on a new contribution.
- Create and test your work.
- Fork the Inchoo Payway repository, or create new branch if you have write permissions to existing repository.
- When creating new branch, following guides must be followed:
- If PR will include bugfix, create branch with following naming: "bugfix/{sort-description|issue-number}"(eg. "bugfix/upgrade-compatibility").
- If PR will include new feature, create branch with following naming: "feature/{sort-description|issue-number}"(eg. "feature/backend-payment").