Add Gaposa brand assets#10148
Open
mwatson2 wants to merge 1 commit intohome-assistant:masterfrom
Open
Conversation
This was referenced Apr 15, 2026
mwatson2
added a commit
to mwatson2/core
that referenced
this pull request
Apr 16, 2026
Before: the four bronze-tier rules that depend on external PRs
(`brands`, `docs-high-level-description`, `docs-installation-instructions`,
`docs-removal-instructions`) were marked as `todo` with the
rationale that they are only truly "done" once the sibling PRs
merge. This was causing the `Check hassfest` CI job to fail with:
Quality scale tier bronze requires quality scale rules to be met:
brands: todo
docs-high-level-description: todo
docs-installation-instructions: todo
docs-removal-instructions: todo
Checking recent merged new-integration PRs shows the actual
convention is to flip these to `done` in the core PR as soon as
the sibling brands and docs PRs are open and under review. Two
concrete recent examples:
- home-assistant#167220 "Add Duco integration" (merged 2026-04-09 21:54 UTC)
had all four rules as `done` in its quality_scale.yaml at the
merge commit e7e4c49. The sibling brands PR home-assistant/brands#10068
merged ~7 hours later at 2026-04-10 04:50 UTC, and the docs PR
home-assistant.io#44468 merged ~9 hours after at 2026-04-10 07:09 UTC.
- home-assistant#166923 "Add Denon rs232 integration" (merged 2026-04-16 16:23 UTC)
also had all four as `done`. The brands PR home-assistant/brands#10058
merged 20 seconds later at 16:24 UTC, and the docs PR
home-assistant.io#44437 is still OPEN at time of this commit —
i.e. the core PR merged before the docs PR even merged.
The sibling PRs for gaposa are open and linked from the main PR:
- brands PR: home-assistant/brands#10148 (asset upload passed validate)
- docs PR: home-assistant/home-assistant.io#44795 (textlint clean,
Copilot review addressed)
Following the same convention here so hassfest passes and the core
PR can proceed through review in parallel with the sibling PRs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
Adds the brand assets (icon and logo, normal and hDPI variants) for the new Gaposa integration. The artwork is derived from the official Gaposa SVG logo at https://www.gaposa.it/res/ftpgaposa/assets/images/logo-n.svg — the circular emblem on the left of the source SVG is used for the icon, and the emblem plus the "GAPOSA" wordmark is used for the logo. All four PNGs are transparent, interlaced, and dimensionally compliant with the brands repository validator.
Type of change
Additional information
Checklist
icon.png)icon@2x.png)logo.png)logo@2x.png)