-
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
Fix broken link in README.md #22135
Fix broken link in README.md #22135
Conversation
Hi @samuel27m. Thank you for your contribution
For more details, please, review the Magento Contributor Assistant documentation |
Hi @ihor-sviziev, thank you for the review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good eye, samuel. There's also another broken link where it says "Bugcrowd researcher crowd." I tried to fix it myself, but it wouldn't allow me to.
@mikeshatch Do you know the specific URL? Maybe you could create a PR yourself to fix that one. There's also another one https://magento.com/security/reporting-magento-security-issue that just redirects to the same broken link you mentioned |
@samuel27m I haven't been able to do a Pull Request since Magento invited me to be a part of their organization. I haven't been able to figure it out yet. That's why I suggested it to you in case you were interested. |
✔️ QA Passed |
@mikeshatch: The Bugcrowd link is already fixed here: #22195 |
It was fixed before I noticed it, you mean? I still see this link as broken: https://bugcrowd.com/magento |
Bugcrowd was replaced with hackerone. That is why there is this PR: https://github.com/magento/magento2/pull/22195/files. So there is no need to take care on the broken link as it will be replaced. |
I see. Thank you! |
Hi @samuel27m, thank you for your contribution! |
Description (*)
Fixed broken link in README.md
Fixed Issues (if relevant)
Manual testing scenarios (*)
Contribution checklist (*)