Add hassfest + HACS validation CI and sync config-flow translations - #12
Open
jgsaez9 wants to merge 2 commits into
Open
Add hassfest + HACS validation CI and sync config-flow translations#12jgsaez9 wants to merge 2 commits into
jgsaez9 wants to merge 2 commits into
Conversation
The translation files referenced an older config flow (user/stt/conversation) so several steps showed raw keys in the UI (most visibly the menu options `add_stt` / `add_conversation`). They also contained an invalid `selector` block that hassfest rejects. Rewrite en.json/de.json and add strings.json to match the real step ids (config: main, menu, add_stt, add_conversation; options: main_options, stt_options, conversation_options), add the menu option labels and the `already_configured` abort reason, and drop the invalid selector block. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- `.github/workflows/validate.yml` runs hassfest and the HACS action (category: integration, ignoring the `brands` check for this custom integration). - Add `hacs.json` so the repository is recognised by HACS. - manifest: add the required `documentation` and `issue_tracker` keys and fix the `requirements` specifier from `>=0.0.0-dev` (invalid PEP 440) to `>=1.0.0`. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
jgsaez9
force-pushed
the
fix/ci-validation
branch
from
July 5, 2026 10:17
3da3400 to
3905daa
Compare
jgsaez9
changed the title
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.
Summary
Adds Home Assistant / HACS validation CI and makes the integration pass it. It also folds in the config-flow translation fixes (needed for hassfest to pass), superseding #10.
Config flow translations
The translation files referenced an older flow (
user/stt/conversation), so steps showed raw keys in the UI (most visibly the menu optionsadd_stt/add_conversation), and they contained an invalidselectorblock. Rewritten to match the real step ids and drop the invalid block.Validation CI
.github/workflows/validate.ymlruns hassfest and the HACS action (category: integration, ignoringbrands).hacs.jsonso the repo is recognised by HACS.documentationandissue_trackerkeys and fixrequirementsfrom>=0.0.0-dev(invalid PEP 440) to>=1.0.0.Validation status
Ran on my fork:
integration_manifestcheck reads the manifest from the repository's default branch, so it reports the missing keys until this is merged tomaster. It also requires the repo to have topics and issues enabled (standard HACS requirements).Supersedes #10.