Reporting Issues on Magento 2 GitHub Repository

Hey everyone!

Late last year the Engineering team gave the Magento community an early New Year’s gift when they announced that we could accept pull requests on the Magento 2 repository. It’s been amazing to collaborate so closely and frequently with everyone. The Magento 2 product is fundamentally better because of these contributions, and we look forward to continued collaboration.

There has been so much interaction on GitHub that we feel it’s time provide some guidance on what issues should be filed there as opposed to being discussed on the community forums (which can be found HERE):

  • Specific Magento 2 bugs should be filed as issues on the Magento 2 repository, preferably with an accompanying pull request
  • Issues with installation, unknown errors, etc. should be started as threads in the forum, and then filed as bugs when enough details are known (and if appropriate)
  • Feature-based pull requests should be discussed with us beforehand (so we don’t duplicate work)

Also, in order to establish the proper rights for contributed code, we need to have every contributor sign a contributor license agreement (CLA). We’ve integrated this check into the pull request process using, and will make that available soon.


2 thoughts on “Reporting Issues on Magento 2 GitHub Repository”

  1. Hi Ben,

    Currently I am facing one issue while doing customization in Magento2.

    I have added custom attribute for customer address and displaying that attribute info on checkout address step.
    But when I tried to proceed for payment step I am getting below exception.

    .CRITICAL: exception ‘LogicException’ with message ‘Report ID: webapi-569e11cd33d49; Message: Property “MyAttribute” does not have corresponding setter in class “Magento\Quote\Api\Data\AddressInterface”.’ in vendor\magento\framework\Webapi\ErrorProcessor.php:194

    I have also defined extension attribute for this interface but not working.

    Could you please help on this.


Leave a Reply

Your email address will not be published. Required fields are marked *