-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Removed email disclosure #39570
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
base: 2.4-develop
Are you sure you want to change the base?
Removed email disclosure #39570
Conversation
Hi @Mohamed-Asar. Thank you for your contribution!
Allowed build names are:
You can find more information about the builds here For more details, review the Code Contributions documentation. |
@magento run all tests. |
Failed to run the builds. Please try to re-run them later. |
@magento run all tests |
@magento create issue |
…Asar/magento2 into remove-email-disclosure
@magento run all tests |
@magento run all tests |
Hello @Mohamed-Asar, Thank you for the contribution! As the related issue has been marked as a Therefore, we are marking this PR as Thanks |
Hello @Mohamed-Asar, We have received approval on this PR from the PO. Therefore, we will proceed with further activities related to it. Thanks |
@magento run all tests |
@magento run Functional Tests B2B, Functional Tests EE, Integration Tests, WebAPI Tests |
Changes done, please review |
@magento run all tests |
Hi @Mohamed-Asar, Thanks for the collaboration & contribution! ✔️ QA PassedPreconditions:
After: ✔️ ![]() Builds are failed. Hence, moving this PR to Extended Testing. Thanks. |
@magento run Functional Tests B2B |
In last two builds test failures for Functional Tests B2B are inconsistent and seems to be flaky. They neither part of PR nor failing because of the PR changes. Hence moving this PR in Merge in Progress |
Description (*)
Display an error message indicating an incorrect email if the entered email is not required to confirm the account, regardless of whether the customer exists or not.
customer/account/confirmation
Contribution checklist (*)
Resolved issues: