Remove trailing slashes and update redirected Ultralytics URLs

[pderrenger]

Summary

Removes terminating path slashes from Ultralytics URLs and refreshes redirected links across the repository.

Trailing slashes (2 fixed, 2 files)

• .github/ISSUE_TEMPLATE/config.yml — https://community.ultralytics.com/ → https://community.ultralytics.com
• .github/ISSUE_TEMPLATE/bug-report.yml — https://docs.ultralytics.com/help/minimum-reproducible-example/ → https://docs.ultralytics.com/help/minimum-reproducible-example

Applied with a regex fixer validated on 17 positive and 15 negative cases (subdomains, protocol-relative, bare host, fragment/query, sentence-final punctuation) before touching the tree. Negatives left untouched and verified in this repo:

• https://github.com/ultralytics/assets/raw/... and other non-Ultralytics paths — slashes there are separators, not terminators.
• server=https%3A%2F%2Fcommunity.ultralytics.com in the Forums badge — URL-encoded parameter, kept byte-identical.
• hello@ultralytics.com in openapi.config.json — email, not a URL.
• https://pypi.org/project/${config.python.project}/ in lib/generators/python.ts — template literal on a non-Ultralytics host.
• https://www.linkedin.com/company/ultralytics/, https://www.gnu.org/licenses/, https://docs.astral.sh/uv/, https://bun.sh/ — not Ultralytics domains, out of scope.
• LICENSE — legal text, skipped.

Redirects (0 accepted, 1 rejected)

All 26 linked URLs were resolved; every Ultralytics link already returns 200 with no redirect (docs.ultralytics.com/help/contributing, /help/CLA, /help/minimum-reproducible-example, /zh/help/contributing, platform.ultralytics.com/api/docs, community.ultralytics.com, www.ultralytics.com/license, www.ultralytics.com/survey?...).

One proposed replacement was rejected after manual inspection:

• https://reddit.com/r/ultralytics → https://www.reddit.com/r/ultralytics/. The chain is 301 to www.reddit.com/r/ultralytics, then a second 301 that re-adds a trailing slash — the exact pattern this PR removes. The source is also the standard Ultralytics social footer replicated verbatim across every Ultralytics repository, so changing it here alone would desync the shared block. Both forms serve the same content.

No dead links and no homepage/index collapses were detected.

Validation

• Re-scanned the tree: zero Ultralytics URLs retain a terminating slash.
• Both changed files parse as YAML and pass prettier@3.8.5 --print-width 120 --check.
• The diff is URL text only; no generated output, lockfiles, or license headers were touched.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updated two Ultralytics links in GitHub issue templates to remove trailing slashes while preserving their destinations.

📊 Key Changes

• Removed the trailing slash from the minimum reproducible example link in .github/ISSUE_TEMPLATE/bug-report.yml.
• Removed the trailing slash from the Community Forum URL in .github/ISSUE_TEMPLATE/config.yml.
• Left non-Ultralytics URLs, URL-encoded values, email addresses, and the Reddit social link unchanged.

🎯 Purpose & Impact

• Issue reporters now follow canonical Ultralytics URLs without terminating slashes.
• The GitHub issue template links remain functionally equivalent; no broader application behavior changed.

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting a ultralytics/openapi 🚀 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/openapi 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 both changed URL-only lines in the issue templates. The trailing-slash removals preserve valid YAML, Markdown links, and GitHub contact-link behavior. LGTM.

[UltralyticsAssistant]

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

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

Your careful cleanup removes trailing slashes from the Ultralytics issue-template links while preserving their destinations, keeping the templates functionally unchanged. Great contribution!