Update Supervisor bug form

[agners]

Proposed change

Update Supervisor bug form to reflect today's naming in the frontend.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (which adds functionality to the supervisor)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to cli pull request:
• Link to client library pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Ruff (ruff format supervisor tests)
• Tests have been added to verify that the new code works.

If API endpoints or add-on configuration are added/changed:

• Documentation added/updated for developers.home-assistant.io
• CLI updated (if necessary)
• Client library updated (if necessary)

Summary by CodeRabbit

• Documentation
  • Updated the bug report instructions for enhanced clarity.
  • Revised the label for system details to clearly refer to "System information."
  • Modified guidance on locating system details and Supervisor diagnostics to reflect the new navigation paths.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request updates the bug report template in .github/ISSUE_TEMPLATE/bug_report.yml. It revises the label and description details for system information and Supervisor diagnostics. The changes provide updated navigation instructions, ensuring that the paths to access system information and diagnostics accurately reflect the new locations in the settings UI.

Changes

File	Change Summary
.github/ISSUE_TEMPLATE/bug_report.yml	- Updated label from "System Health information" to "System information". - Revised description for system information to specify "Settings -> System -> Repairs -> (three dot menu) -> System Information". - Updated Supervisor diagnostics instructions from "Settings -> Integrations" to "Settings -> Devices & services".

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 176e511 and b85fb32.

📒 Files selected for processing (1)

• .github/ISSUE_TEMPLATE/bug_report.yml (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Build armhf supervisor
• GitHub Check: Run tests Python 3.13.2

🔇 Additional comments (3)

.github/ISSUE_TEMPLATE/bug_report.yml (3)

29-29: Updated Installation Description

The description for the "What type of installation are you running?" dropdown now correctly directs users to the new location using the three dot menu. This change aligns with the updated frontend naming conventions, ensuring clarity on where to locate the installation type information.

---

75-79: Revised System Information Field

The label has been updated from "System Health information" to "System information" and the instructions now clearly explain how to navigate to "Settings -> System -> Repairs -> (three dot menu) -> System Information." This update enhances clarity and consistency with the current UI.

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 79-79: trailing spaces

(trailing-spaces)

---

86-88: Updated Supervisor Diagnostics Instructions

The instructions for accessing Supervisor diagnostics have been revised to reference "Settings -> Devices & services" instead of "Settings -> Integrations." This update ensures that the bug report template reflects the current navigation within the frontend.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.