Standardize .github configuration

[glenn-jocher]

Aligns `.github/` with the reference configuration used in `ultralytics/sdk`, `skills`, `openapi` and `lite`.

• `format.yml`: standard triggers (`issues: [opened]`, `pull_request` on `main`); remove the checkout + nightly `cargo fmt --check` steps, which `ci.yml` already runs on every push and PR.
• `bug-report.yml`: components, environment and reproducible-example fields now describe the Rust crate, CLI and npm package instead of the Python package.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Standardizes the repository’s GitHub issue template and formatting workflow for YOLO Rust inference by aligning them with the shared configuration used by related Ultralytics repositories.

📊 Key Changes

• Renamed the bug report description to target Ultralytics YOLO Rust inference.
• Replaced Python-focused issue components with Rust crate, CLI, model-loading, prediction, video, visualization, hardware acceleration, and WebGPU options.
• Updated environment details to request Rust toolchain, crate features, model, hardware, and npm/browser information where relevant.
• Changed the reproducible-example placeholder from Python code to an ultralytics-inference CLI command.
• Standardized format.yml to run for newly opened issues and pull requests targeting main, while removing its redundant checkout and nightly cargo fmt --check steps already covered by ci.yml.

🎯 Purpose & Impact

• Bug reports now collect information specific to the Rust crate, CLI, and npm package, aligning submissions with this repository’s components.
• Formatting checks remain handled by ci.yml on pushes and pull requests, while format.yml uses the shared workflow trigger configuration.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/inference 🚀 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/inference 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 files. The workflow trigger standardization and removal of the duplicate Rust formatting step are consistent with the repository CI configuration. The issue template has one bounded gap: its newly advertised npm/WebGPU component is not supported by the required Rust-only environment and reproduction fields.

💬 Posted 1 inline comment

• 📝 LOW .github/ISSUE_TEMPLATE/bug-report.yml:61 Selecting WebGPU (npm) still requires Rust-specific environment details, while the required reproducible example below is a Rust CLI command. Reports for @ultralytics/yolo therefore omit the npm package version, Node/package manager, browser, WebGPU/CPU mode, and secure-context details needed to reproduce them. Add an npm/browser block to the required environment and a JavaScript example, or split the form by component.

[glenn-jocher]

Added an npm/browser line to the environment placeholder. The reproducible-example placeholder stays a single Rust CLI command; splitting the form by component is more than this template needs.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[glenn-jocher]

Added an npm/browser line to the environment placeholder. The reproducible-example placeholder stays a single Rust CLI command; splitting the form by component is more than this template needs.

[UltralyticsAssistant]

🔍 PR Review 2

_{Made with ❤️ by Ultralytics Actions}

Review 2: the prior issue was addressed by adding npm/browser details to the environment prompt. The workflow trigger changes, removal of the duplicate formatting steps, and updated Rust-specific issue template are consistent with the repository configuration. No new concrete issues found. LGTM.

Superseded by new review

[UltralyticsAssistant]

🔍 PR Review 3

_{Made with ❤️ by Ultralytics Actions}

Review 3: the prior WebGPU environment finding remains addressed. The current changes standardize the Rust issue template and restrict workflow triggers to newly opened issues and pull requests targeting main. No new concrete defects were found in the changed lines. LGTM.

[UltralyticsAssistant]

🎉 PR #426 has been merged—thank you, @glenn-jocher!

“Alone we can do so little; together we can do so much.” — Helen Keller

This collaboration standardizes issue reporting and formatting workflows for YOLO Rust inference, making component-specific bug reports clearer while keeping formatting checks aligned with the shared CI configuration.