- Do not open up a GitHub issue if the bug is a security vulnerability in FACT-Finder-Web-Components Magento2-Module..
- Ensure the bug was not already reported by searching on GitHub under Issues.
- If you're unable to find an open issue addressing the problem, open a new one. Be sure to include all relevant information just by filling the report template.
- Open a new GitHub pull request with the patch.
- Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable just by filling the PR template.
- Before submitting, please make sure you follow all common coding guidelines and in case of new features a basic test coverage is given.
- Changes that are cosmetic in nature and do not add anything substantial to the stability, functionality, or testability of the FACT-Finder-Web-Components Magento2-Module will usually not be accepted.
- Create first an issue and then start coding to contribute via a PR.
- Contributions must adhere to our coding standards, which are based on
magento/magento-coding-standard
. You can find more details in the phpcs.xml.dist included. - Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Please use our template while creating pull request
- For any change which could be notified, please update the CHANGELOG.md with relative change info.
- PRs which include bug fixes must be accompanied by a step-by-step description of how to reproduce the bug.
- Ask your question via an issue which is prefixed with
question
in the title.
Thanks!
Your FACT-Finder Team