Remove trailing slashes and update redirected Ultralytics URLs

[pderrenger]

Normalizes Ultralytics links in this repository to their canonical, non-redirecting form.

Trailing slashes removed (5 across 3 files)

• README.md — logo link https://www.ultralytics.com/, Forums badge target https://community.ultralytics.com/, docs link https://docs.ultralytics.com/
• .github/ISSUE_TEMPLATE/config.yml — Forum contact link https://community.ultralytics.com/
• .github/ISSUE_TEMPLATE/bug-report.yml — https://docs.ultralytics.com/help/minimum-reproducible-example/

All five destinations were verified to return HTTP 200 with no redirect in their slash-free form. A repo-wide re-scan confirms zero remaining terminating slashes on ultralytics.com or any *.ultralytics.com URL. Path separators, the percent-encoded server=https%3A%2F%2Fcommunity.ultralytics.com badge parameter, and the ultralytics.com/license headers written by Ultralytics Actions were left byte-identical.

Redirects reviewed, none baked in

Every URL in the repository was resolved serially; four redirect candidates were deliberately rejected:

• https://ultralytics.com/discord → https://discord.com/invite/ultralytics — vanity shortlink wrapping an expiring invite; the shortlink is the durable form.
• https://ultralytics.com/license → https://www.ultralytics.com/license — license-header string owned and rewritten by Ultralytics Actions; changing it would desync from the tool output.
• https://reddit.com/r/ultralytics → https://www.reddit.com/r/ultralytics/ — host canonicalization rather than a content move, and the destination re-adds a trailing slash. Kept to match the shared social-badge block used across Ultralytics repositories.
• .gitignore template provenance comments pointing at github.com/github/gitignore/blob/master/... now resolve to /blob/main/... (GitHub default-branch rename). Left as provenance records for the copied templates; no functional impact.

Dead link flagged for follow-up

functions/MarchingCubes.m:21 cites http://www.mhelm.de/octave/m/marching_cube.m as the origin of the adapted Octave implementation. That host now redirects to null-a.de, which no longer resolves. It is an authorship attribution for third-party code, so it was left untouched — a human should decide whether to keep it as a historical citation or point it at an archived copy. This is pre-existing and unrelated to this diff.

Validation

• Prettier 3.8.5 (--print-width 120) reports no formatting changes for README.md and all workflow/issue-template YAML.
• All six YAML files parse cleanly.
• No MATLAB sources are modified; the diff is URL text only.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updated five Ultralytics URLs in the README and GitHub issue templates to use canonical forms without trailing slashes, avoiding redirects.

📊 Key Changes

• Removed trailing slashes from the Ultralytics homepage, Community Forum, documentation, and minimum reproducible example links.
• Updated the README logo, Forums badge, and documentation links.
• Updated the Forum contact link in .github/ISSUE_TEMPLATE/config.yml and the documentation link in .github/ISSUE_TEMPLATE/bug-report.yml.
• Left other reviewed URLs and provenance comments unchanged, including the Discord, license, Reddit, and third-party citation links.

🎯 Purpose & Impact

• Links now use their verified non-redirecting forms where changed, while the repository’s URL text and MATLAB sources remain otherwise unchanged.

[UltralyticsAssistant]

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

Reviewed all 10 changed lines across the three URL-only files. The trailing-slash removals preserve valid Markdown and GitHub issue-template links, with no concrete behavioral regression identified. LGTM.

[UltralyticsAssistant]

🎉 PR #34 has been merged—thank you, @pderrenger!

“Great things are done by a series of small things brought together.” — Vincent van Gogh

This PR brings together several small URL updates to keep README and issue-template links in their verified canonical forms without trailing slashes or redirects.