-
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
Stale links to topics migrated to Adobe domains #36230
Comments
Hi @Tomasito665. Thank you for your report.
Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
For more details, review the Magento Contributor Assistant documentation. Add a comment to assign the issue: To learn more about issue processing workflow, refer to the Code Contributions.
🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket. ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
Hello @Tomasito665 Could you please be more specific or provide more details about where exact wrong links? Template in use: https://github.com/magento/magento2/blob/2.4-develop/.github/PULL_REQUEST_TEMPLATE.md For issues, all templates can be found https://github.com/magento/magento2/tree/2.4-develop/.github/ISSUE_TEMPLATE
Noteі:
|
Hello @sdzhepa, Thanks for coming back to me. If you click New issue → Developer experience issue, the template still contains the old links. Many links on other documentation are also old, including some links on the main README. A few examples:
For more examples, search for
I agree. |
Hi @engcom-November. Thank you for working on this issue.
|
Hi @Tomasito665 , |
Hi @engcom-November, I filed a pull request to update all links to migrated documentation to their updated URLs. It has been two days since I filed the PR and yet CI checks appear in progress still. How long do they normally take? Am I missing something? Thanks |
Hi @Tomasito665 , |
Hi @engcom-November, Thanks for your response. The issue you describe is about building in redirects from the old to the new URLs in the Magento docs repo, which is related but different than the issue described in this issue. In this issue, I refer to the URLs in this repository, magento2, which point to the old URLs. The pull request I opened updates all links to their new locations, removing the need to redirect at all. Because of that, I would like to reopen the issue until the pull request is closed. Could you do that? Thank you! |
Summary (*)
Adobe migrated Magento documentation to Adobe domains.
https://devdocs.magento.com/migrated.html
Examples (*)
The pull request description template itself is a clear example:
The link points to https://devdocs.magento.com/guides/v2.4/contributor-guide/contributing.html#backlog, which was moved to https://developer.adobe.com/commerce/contributor/guides/code-contributions/#community-backlog-priority.
Proposed solution
The solution is simple enough: update the links :-)
Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.
The text was updated successfully, but these errors were encountered: