Remove trailing slashes and update redirected Ultralytics URLs

[pderrenger]

Canonicalizes every Ultralytics URL in the repository to its slash-free form and re-checks all outbound links against their live redirect destinations.

Trailing slashes

9 terminating path slashes removed across 5 files. Only slashes that end a path were touched — path separators, URL-encoded URLs, and third-party hosts are untouched.

File	Change
README.md	www.ultralytics.com/ ×2 (logo link, intro link), docs.ultralytics.com/models/yoloe/, community.ultralytics.com/ (Forums badge target)
.github/ISSUE_TEMPLATE/config.yml	docs.ultralytics.com/models/yoloe/, community.ultralytics.com/
.github/ISSUE_TEMPLATE/bug-report.yml	docs.ultralytics.com/models/yoloe/, docs.ultralytics.com/help/minimum-reproducible-example/
.github/ISSUE_TEMPLATE/feature-request.yml	docs.ultralytics.com/models/yoloe/
.github/ISSUE_TEMPLATE/question.yml	docs.ultralytics.com/models/yoloe/

Deliberately left as-is:

• https://img.shields.io/discourse/users?server=https%3A%2F%2Fcommunity.ultralytics.com&... — a URL-encoded URL inside a badge query parameter; it must stay byte-identical for the badge to render, and it has no trailing slash anyway.
• https://ultralytics.com/discord and https://ultralytics.com/bilibili — vanity shortlinks that are meant to stay redirects.
• https://ultralytics.com/license headers in all 13 Python/shell files — written by Ultralytics Actions and already slash-free.
• LICENSE — legal text, excluded from the sweep.

Redirect refresh

All 26 unique HTTP links in the repository were resolved against their live destinations. One replacement was proposed and rejected:

• https://reddit.com/r/ultralytics → https://www.reddit.com/r/ultralytics/ — rejected. The bare-host → www hop is a real 301, but the resolved destination only differs by host canonicalization plus a re-added trailing slash (verified: reddit.com/r/ultralytics 301s to www.reddit.com/r/ultralytics with no slash; the slash is added by Reddit's own canonicalizer on browser user agents). Rewriting it here would also diverge this repo's footer and issue-template links from the shared Ultralytics README/issue-template block used org-wide. If the www form is preferred it should be changed centrally in the template rather than in one repo.

No dead links and no broken destinations were reported.

Validation

• Full diff reviewed line by line: URL text only, no logic or prose changes.
• Zero Ultralytics URLs keep a terminating slash after the sweep (re-verified with an independent scan).
• All six .github YAML files parse cleanly.
• prettier@3.8.5 --print-width 120 --check passes on the changed Markdown and YAML.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Canonicalized Ultralytics links by removing trailing path slashes in the README and issue templates, without changing repository logic or prose.

📊 Key Changes

• Updated YOLOE documentation links to use https://docs.ultralytics.com/models/yoloe.
• Removed trailing slashes from Ultralytics website and community forum links in README.md.
• Updated the minimum reproducible example documentation link in the bug report template.
• Preserved vanity redirects, URL-encoded badge parameters, and the existing Reddit link.
• Validation reported clean YAML parsing and successful Prettier checks for the changed Markdown and YAML files.

🎯 Purpose & Impact

• Links now use the repository’s slash-free Ultralytics URL format, while issue-template navigation and README destinations remain functionally unchanged.

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting a ultralytics/yoloe_data_engine 🚀 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/yoloe_data_engine 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}

LGTM. Reviewed all five changed files; the PR only removes terminating slashes from existing URLs, with no logic, YAML structure, or behavioral regressions introduced.

[UltralyticsAssistant]

🎉 Thank you @pderrenger for the merged PR #9!

“The details are not the details. They make the design.” — Charles Eames

Your careful link canonicalization keeps README and issue-template URLs consistent while preserving existing navigation, redirects, and repository content.