-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[32027][To 2.4-develop] Marked Framework interfaces as API part 4 #32728
[32027][To 2.4-develop] Marked Framework interfaces as API part 4 #32728
Conversation
Hi @Usik2203. Thank you for your contribution
❗ Automated tests can be triggered manually with an appropriate comment:
You can find more information about the builds here ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review. For more details, please, review the Magento Contributor Guide documentation. 🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket. 🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
@magento run all tests |
@magento run Functional Tests B2B, Functional Tests CE, Functional Tests EE, WebAPI Tests |
I confirm the PR covers all the changes requested in the related Issue. Waiting for tests to finish in order to approve. |
@magento run Functional Tests EE, WebAPI Tests |
Hi @aleron75 |
As mentioned with Sergii Ivashchenko static tests are ok |
@gabrieldagama, an error occurred during the Pull Request import. |
1 similar comment
@gabrieldagama, an error occurred during the Pull Request import. |
@gabrieldagama the branch with code successfully imported into |
Hi @Usik2203, thank you for your contribution! |
Description (*)
This PR fixes #32027
Related Pull Requests
#32170
Fixed Issues (if relevant)