Skip to content

fix: add missing CONFIG_SCHEMA and service translations #552

fix: add missing CONFIG_SCHEMA and service translations

fix: add missing CONFIG_SCHEMA and service translations #552

Triggered via pull request July 27, 2023 14:12
Status Failure
Total duration 2m 9s
Artifacts

pull.yml

on: pull_request
Validate
2m 2s
Validate
Check style formatting
13s
Check style formatting
Run tests
50s
Run tests
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 3 warnings
Validate
[SERVICES] Service api has no name and is not in the translations file
Validate
[SERVICES] Service polling_interval has no name and is not in the translations file
Validate
[TRANSLATIONS] Invalid strings.json: expected a dictionary for dictionary value @ data['services']['api']['fields']['command']. Got 'Command'
Validate
Process completed with exit code 1.
Check style formatting
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run tests
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Validate
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/