newsupernova/vendor/magento/data-migration-tool/.github/CONTRIBUTING.md

Contributing to Data Migration Tool code

Contributions to the Data Migration Tool codebase are done using the fork & pull model. This contribution model has contributors maintaining their own copy of the forked codebase (which can easily be synced with the main copy). The forked repository is then used to submit a request to the base repository to “pull” a set of changes. For more information on pull requests please refer to GitHub Help.

Contributions can take the form of new components or features, changes to existing features, tests, documentation (such as developer guides, user guides, examples, or specifications), bug fixes or optimizations.

The Data Migration Tool development team will review all issues and contributions submitted by the community of developers in the first in, first out order. During the review we might require clarifications from the contributor. If there is no response from the contributor within two weeks, the pull request will be closed.

Contribution requirements

1. Contributions must adhere to the Magento coding standards.
2. Pull requests (PRs) must be accompanied by a meaningful description of their purpose. Comprehensive descriptions increase the chances of a pull request being merged quickly and without additional clarification requests.
3. Commits must be accompanied by meaningful commit messages. Please see the Pull Request Template for more information.
4. PRs which include bug fixes must be accompanied with a step-by-step description of how to reproduce the bug.
5. PRs which include new logic or new features must be submitted along with:
6. Unit/integration test coverage
7. Proposed documentation updates. Documentation contributions can be submitted via the devdocs GitHub.

Contribution process

If you are a new GitHub user, we recommend that you create your own free github account. This will allow you to collaborate with the Data Migration Tool development team, fork the the tool project and send pull requests.

1. Search current listed issues (open or closed) for similar proposals of intended contribution before starting work on a new contribution.
2. Review the Contributor License Agreement if this is your first time contributing.
3. Create and test your work.
4. Fork the Data Migration Tool repository.
5. Once your contribution is received the Data Migration Tool development team will review the contribution and collaborate with you as needed.

Code of Conduct

Please note that this project is released with a Contributor Code of Conduct. We expect you to agree to its terms when participating in this project. The full text is available in the repository Wiki.