Fix redirected URLs

[glenn-jocher]

Summary

• update redirected external URLs to their final destinations
• apply the redirect cleanup across tracked documentation and related text files

Testing

• no tests run (link-only changes)

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

🛠️ This PR makes small but useful documentation and link fixes across YOLOv5, improving link reliability, accuracy, and overall user guidance.

📊 Key Changes

• 🔗 Updated several outdated or inconsistent URLs in README.md, README.zh-CN.md, workflow docs, and ClearML docs.
• ▶️ Standardized YouTube links to use www.youtube.com instead of the shorter youtube.com format.
• 📄 Fixed AGPL-3.0 license links in both English and Chinese READMEs to point to the correct OSI page.
• ⚙️ Corrected the CUDA reference link in .github/workflows/format.yml from cuda-zone to the current CUDA page.
• 🤖 Updated the TensorFlow Lite metadata documentation link in export.py to the newer Google AI Edge docs path.
• 🌐 Adjusted the Chinese README’s Ultralytics App link to point to the main Ultralytics site instead of the previous app install page.
• ☁️ Updated the ClearML remote execution documentation link to point to the Ultralytics Platform docs page.

🎯 Purpose & Impact

• ✅ Reduces broken, outdated, or redirected links, making documentation easier to trust and navigate.
• 📚 Improves the onboarding experience for new users by keeping setup, licensing, and platform references current.
• 🌍 Keeps English and Chinese documentation more consistent and accurate.
• 🔧 Helps developers and users find the right external resources faster, especially for export, licensing, cloud training, and integrations.
• 🚀 No model code or training behavior changes are introduced, so impact is limited to documentation quality and usability.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/yolov5 🚀 PR! This is an automated message to help with review readiness, and an engineer will assist you shortly 😊 Please review the checklist below:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/yolov5 main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

The redirect cleanup looks good overall, but the README changes for Ultralytics App introduce a documentation regression by sending users to the generic homepage instead of the actual platform/app entrypoint. Aside from that, the PR is clean.

💬 Posted 2 inline comments

[UltralyticsAssistant]

🎉 Huge thanks for getting this merged, @glenn-jocher — these kinds of thoughtful documentation updates make a real difference.

As Leonardo da Vinci said, “Details make perfection, and perfection is not a detail.” This PR is a great example of that mindset: by fixing links, improving consistency, and keeping guidance current across YOLOv5 docs, you’ve made the project more reliable and welcoming for everyone who depends on it.

Really appreciate the care behind these quality-of-life improvements — they strengthen the experience for the whole community. 🙌