Standardize .github configuration

[glenn-jocher]

• Add the issues: opened trigger and issues: write permission to format.yml so Ultralytics Actions labels new issues, matching the org standard.
• Add bug-report, feature-request and question issue templates modeled on the org standard, tailored to the HUB web app, and enable blank issues in config.yml.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Standardized the repository’s issue intake and automation by adding HUB-specific issue templates, enabling blank issues, and allowing the Actions workflow to process newly opened issues.

📊 Key Changes

• Added bug report, feature request, and question forms with predefined labels and HUB-specific fields.
• Updated the forms to direct active Platform issues to the Platform documentation and ultralytics/sdk.
• Enabled blank issue submissions and added Platform SDK, Reddit, Forum, and Discord contact links.
• Updated format.yml to trigger on newly opened issues and grant issues: write permission for issue comments and labels.

🎯 Purpose & Impact

• New issue authors receive structured forms for common request types, while maintainers can use the existing automated actions on opened issues.
• Users can still submit unstructured issues and have additional support destinations available through the issue chooser.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/hub 🚀 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/hub 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 .github/workflows/format.yml. The issues: opened trigger and issues: write permission correctly enable Ultralytics Actions to label newly opened issues without regressing the existing pull-request workflow. LGTM.

Superseded by new review

[UltralyticsAssistant]

🔍 PR Review 2

_{Made with ❤️ by Ultralytics Actions}

Review 2: the previous format.yml change remains addressed. The newly added issue intake introduces stale HUB support guidance and a missing default label; these issues should be corrected before merge.

💬 Posted 2 inline comments

• 💡 MEDIUM .github/ISSUE_TEMPLATE/config.yml:3 AGENTS.md says this repository is historical and HUB shut down on July 31, 2026; it contains only Platform redirects/workflows, and HUB APIs/services no longer work. Enabling blank issues together with the three new HUB-branded forms creates a live-looking support intake for an unsupported product, directing users to report HUB bugs, features, and API issues here. Retarget the intake to Platform, or leave issue creation disabled.
• 📝 LOW .github/ISSUE_TEMPLATE/bug-report.yml:6 The repository's current label set does not contain triage, and GitHub does not create missing labels when applying issue-form defaults. Bug reports from this form will therefore silently receive bug but not triage, defeating the intended triage behavior. Add the label in repository settings or remove it from the form. (github.com)

[UltralyticsAssistant]

🔍 PR Review 3

_{Made with ❤️ by Ultralytics Actions}

Since review 2, the forms now disclose HUB's retirement and add a Platform SDK contact link; the workflow change remains addressed. Two issues remain unresolved: this historical repository still exposes HUB issue intake and blank issues, and the bug form still references a missing triage label. Not LGTM.

💬 Posted 2 inline comments

• 💡 MEDIUM .github/ISSUE_TEMPLATE/config.yml:3 Although the forms now mention the retirement date, this still enables a live HUB support intake: visitors can submit blank issues or use HUB-branded bug, feature, and question forms whose components describe the retired web app. This repository is now historical and contains only redirects/workflows, so these submissions have no supported owner after July 31, 2026. Disable issue creation (and remove the forms), or retarget the entire intake to a currently supported repository.
• 📝 LOW .github/ISSUE_TEMPLATE/bug-report.yml:6 triage is still not an existing repository label, so bug reports created from this form will receive bug but silently omit triage; GitHub does not automatically add labels that do not already exist. Remove triage here or create the label in the repository settings.

[glenn-jocher]

Re Review 3: both remaining findings are intentional per the org standard — every Ultralytics public repository carries the full issue template set with blank issues enabled; the forms disclose HUB's retirement and route active Platform support to the Platform API docs and ultralytics/sdk issues, and remain for issues with this historical repository itself. The triage label already exists in this repository.

[UltralyticsAssistant]

🔍 PR Review 4

_{Made with ❤️ by Ultralytics Actions}

Reviewed all five changed files. The workflow changes remain correct, and the earlier HUB-intake and triage concerns are settled by the author’s clarification. One remaining issue is that the new Platform SDK support link leads to a repository where issue creation is restricted, so the advertised reporting route does not work. (github.com)

💬 Posted 1 inline comment

• 📝 LOW .github/ISSUE_TEMPLATE/config.yml:12 This newly added destination cannot accept reports: the ultralytics/sdk Issues page currently states that issue creation is restricted. Users following this link—or the same link repeated in all three forms—will be unable to file the promised active Platform SDK bug or feature report. Replace every occurrence with a support destination that accepts issues, or remove this contact link. (github.com)

[glenn-jocher]

Re Review 4: the ultralytics/sdk destination is the mandated Platform SDK support route (its own issue templates and Platform API reference point there). The "issue creation is restricted" banner is a repository setting on ultralytics/sdk, not something this template can fix; flagged for the repository owner to lift there.

[UltralyticsAssistant]

🔍 PR Review 5

_{Made with ❤️ by Ultralytics Actions}

Since review 4, no new repository-local defect or regression is introduced in the five-file diff. The workflow trigger/permission change and issue-template configuration remain consistent with the stated org standard, and the previously discussed external SDK destination concern is outside this PR's files. LGTM.

[UltralyticsAssistant]

🎉 Thank you, @glenn-jocher, for the merged PR #1324!

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

This PR brings together HUB-specific issue forms, blank issue support, helpful contact links, and updated automation triggers to create a more structured and accessible issue intake experience.