Merge pull request #64 from mdeweerd:flow #1
validate-hacs.yml
on: push
validate
1m 20s
HACS Action
24s
Annotations
9 errors and 2 warnings
HACS Action
<Validation hacsjson> failed: The repository has no 'hacs.json' file (More info: https://hacs.xyz/docs/publish/include#check-hacs-manifest )
|
HACS Action
<Validation topics> failed: The repository has no valid topics (More info: https://hacs.xyz/docs/publish/include#check-repository )
|
HACS Action
<Validation brands> failed: The repository has not been added as a custom domain to the brands repo (More info: https://hacs.xyz/docs/publish/include#check-brands )
|
HACS Action
<Validation integration_manifest> failed: required key not provided @ data['issue_tracker'] (More info: https://hacs.xyz/docs/publish/include#check-manifest )
|
HACS Action
<Integration custom-components/climate.programmable_thermostat> 4/8 checks failed
|
validate
[MANIFEST] Domain is missing an IoT Class
|
validate
[SERVICES] Service reload has no name and is not in the translations file
|
validate
[TRANSLATIONS] Invalid translations/en.json: extra keys not allowed @ data['options']['title']. Got 'Programmable thermostat'
|
validate
Process completed with exit code 1.
|
validate
[CONFIG_SCHEMA] Integrations which implement 'async_setup' or 'setup' must define either 'CONFIG_SCHEMA', 'PLATFORM_SCHEMA' or 'PLATFORM_SCHEMA_BASE'. If the integration has no configuration parameters, can only be set up from platforms or can only be set up from config entries, one of the helpers cv.empty_config_schema, cv.platform_only_config_schema or cv.config_entry_only_config_schema can be used.
|
validate
[TRANSLATIONS] config.title key has been moved out of config and into the root of strings.json. Starting Home Assistant 0.109 you only need to define this key in the root if the title needs to be different than the name of your integration in the manifest.
|