2.5 minute read
Adobe Commerce and Handling Pull Requests on Github
Adobe Commerce is a powerful and flexible eCommerce platform used by businesses around the world. Open source code allows developers to make changes and additions to the underlying source code and then share their changes with the broader Adobe Commerce community.
One way for developers to share changes is to submit a pull request on GitHub. A pull request (PR) is an automated request that asks a project maintainer (most likely a member of the Adobe team) to review and incorporate a change made by an external collaborator. It can be anything – a bug fix, an improvement, or a new feature. Once your request is accepted, the changes will be integrated into the core Adobe Commerce code and will be publicly available. When Adobe Commerce receives a pull request, it follows a clearly defined process to review and accept or reject proposed changes.
First, the project maintainer performs a basic review of the pull request to ensure that it has all the necessary information and evidence to support the changes. They then run tests to see if the code works properly. If the proposed changes pass all tests, the pull request is accepted and the changes are then published. However, if problems arise or any of the tests fail, the pull request will be rejected and the contributor will have to resubmit or edit the changes until all tests pass.
In summary, the Adobe Commerce platform leverages GitHub and the ability to submit pull requests to ensure that bugs and features are thoroughly tested before they are released to the public. This process helps maintain product quality and provide a better experience to end users. With the ability to submit pull requests, Adobe Commerce encourages external contributions and helps keep the platform modern and state-of-the-art.