-
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
Bugfix/26156 luma theme banner css 1024px #30761
Bugfix/26156 luma theme banner css 1024px #30761
Conversation
…/26516-luma-theme-banner-css-1024px
Hi @chiranjeevi-cj. 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 give me test instance - deploy test instance based on PR changes |
Hi @chiranjeevi-cj. Thank you for your request. I'm working on Magento instance for you. |
Hi @chiranjeevi-cj, here is your Magento Instance: https://5d6b29f44a7a945091f3365efaef0825.instances.magento-community.engineering |
@magento run all tests |
Hi @chiranjeevi-cj, I see we already have Pull Request that does the correct fix in the sample data module magento/magento2-sample-data#146, so I'm closing this PR as not relevant. Thank you so much for your contribution! |
Hi @chiranjeevi-cj, thank you for your contribution! |
Description (*)
Fixed Issues (if relevant)
Manual testing scenarios (*)
Contribution checklist (*)