Skip to content

Fix broken Jetson Nano link on YOLO26 vs YOLOv9 compare page - #371

Open
raimbekovm wants to merge 1 commit into
mainfrom
fix-jetson-nano-link
Open

raimbekovm wants to merge 1 commit into
mainfrom
fix-jetson-nano-link

Conversation

@raimbekovm

@raimbekovm raimbekovm commented Oct 21, 2026 •

Copy link
Copy Markdown
Member

summary

  • developer.nvidia.com/embedded/jetson-nano-developer-kit now 301s to an NVIDIA page that returns 404 to the link checker, failing the docs.ultralytics.com broken-links run.
  • Point the link at the Ultralytics NVIDIA Jetson guide, matching the 17 other compare/ pages that link Jetson there.

measured

link status in link check
developer.nvidia.com/embedded/jetson-nano-developer-kit 404 after 1 redirect
docs.ultralytics.com/guides/nvidia-jetson 200

🤖 Generated with Claude Code

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Updated the NVIDIA Jetson Nano link on the YOLO26 vs YOLOv9 comparison page to use the Ultralytics Jetson guide instead of the broken NVIDIA URL.

📊 Key Changes

  • Replaced the NVIDIA Jetson Nano link with https://docs.ultralytics.com/guides/nvidia-jetson.
  • Kept the surrounding edge-device inference text unchanged.

🎯 Purpose & Impact

  • The comparison page now directs readers to the Ultralytics Jetson guide rather than the NVIDIA URL reported as returning 404 by the link checker.

@UltralyticsAssistant UltralyticsAssistant added documentation Improvements or additions to documentation fixed Bug has been resolved labels Oct 21, 2026
@UltralyticsAssistant

Copy link
Copy Markdown
Member

👋 Hello @raimbekovm, thank you for submitting a ultralytics/docs 🚀 PR! This automated message confirms your contribution was received, and an Ultralytics engineer will assist with the review. To ensure a seamless integration of your work, please review the following checklist:

  • ✅ 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/docs 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; the CLA check will comment with signing instructions if needed.
  • ✅ 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 UltralyticsAssistant left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 PR Review

Made with ❤️ by Ultralytics Actions

Reviewed the single link replacement. No issues found; LGTM.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation fixed Bug has been resolved

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants