Skip to content

Change quality scale from legacy to bronze#43620

Closed
Poshy163 wants to merge 1 commit into
home-assistant:nextfrom
Poshy163:patch-10
Closed

Change quality scale from legacy to bronze#43620
Poshy163 wants to merge 1 commit into
home-assistant:nextfrom
Poshy163:patch-10

Conversation

@Poshy163
Copy link
Copy Markdown
Contributor

@Poshy163 Poshy163 commented Feb 19, 2026

Proposed change

Type of change

  • Spelling, grammar or other readability improvements (current branch).
  • Adjusted missing or incorrect information in the current documentation (current branch).
  • Added documentation for a new integration I'm adding to Home Assistant (next branch).
  • Added documentation for a new feature I'm adding to Home Assistant (next branch).
  • Removed stale or deprecated documentation.

Additional information

Checklist

  • This PR uses the correct branch, based on one of the following:
    • I made a change to the existing documentation and used the current branch.
    • I made a change that is related to an upcoming version of Home Assistant and used the next branch.
  • The documentation follows the Home Assistant documentation standards.

Copilot AI review requested due to automatic review settings February 19, 2026 03:05
@home-assistant home-assistant Bot added in-progress This PR/Issue is currently being worked on needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch next This PR goes into the next branch labels Feb 19, 2026
@home-assistant
Copy link
Copy Markdown

It seems that this PR is targeted against an incorrect branch. Documentation updates which apply to our current stable release should target the current branch. Please change the target branch of this PR to current and rebase if needed. If this is documentation for a new feature, please add a link to that PR in your description.

@netlify
Copy link
Copy Markdown

netlify Bot commented Feb 19, 2026

Deploy Preview for home-assistant-docs ready!

Name Link
🔨 Latest commit b3cf7fe
🔍 Latest deploy log https://app.netlify.com/projects/home-assistant-docs/deploys/69967dee4374d800084766d1
😎 Deploy Preview https://deploy-preview-43620--home-assistant-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@home-assistant home-assistant Bot added has-parent This PR has a parent PR in another repo and removed needs-rebase The PR has been branched of the wrong base branch or targets an incorrect target branch labels Feb 19, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request updates the Integration Quality Scale metadata for the Ness Alarm integration from "legacy" to "bronze". The Integration Quality Scale is Home Assistant's system for categorizing integration quality based on code standards, documentation, testing, and other criteria that were revised in the December 2024 release.

Changes:

  • Updated the ha_quality_scale field in the Ness Alarm integration documentation from legacy to bronze

@c0ffeeca7
Copy link
Copy Markdown
Contributor

For the quality scale change, a docs PR shouldn't even be needed. Once the quality scale is updated in core, the documentation should be updated automatically.

https://developers.home-assistant.io/docs/documenting/create-page#about-the-integration-page-header-format

@c0ffeeca7 c0ffeeca7 closed this Feb 19, 2026
@home-assistant home-assistant Bot removed the in-progress This PR/Issue is currently being worked on label Feb 19, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators Feb 20, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

has-parent This PR has a parent PR in another repo next This PR goes into the next branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants