meteocat 4.0.0 β†’ 4.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (49) hide show
  1. package/.github/ISSUE_TEMPLATE/bug_report.md +45 -45
  2. package/.github/ISSUE_TEMPLATE/config.yml +8 -8
  3. package/.github/ISSUE_TEMPLATE/improvement.md +39 -39
  4. package/.github/ISSUE_TEMPLATE/new_function.md +41 -41
  5. package/.github/labels.yml +63 -63
  6. package/.github/workflows/autocloser.yaml +27 -27
  7. package/.github/workflows/close-on-label.yml +48 -48
  8. package/.github/workflows/force-sync-labels.yml +18 -18
  9. package/.github/workflows/hassfest.yaml +13 -13
  10. package/.github/workflows/publish-zip.yml +67 -67
  11. package/.github/workflows/release.yml +41 -41
  12. package/.github/workflows/stale.yml +63 -63
  13. package/.github/workflows/sync-gitlab.yml +107 -107
  14. package/.github/workflows/sync-labels.yml +21 -21
  15. package/.github/workflows/validate.yaml +16 -16
  16. package/.pre-commit-config.yaml +37 -37
  17. package/.releaserc +37 -37
  18. package/AUTHORS.md +13 -13
  19. package/CHANGELOG.md +963 -954
  20. package/README.md +207 -207
  21. package/conftest.py +11 -11
  22. package/custom_components/meteocat/__init__.py +298 -298
  23. package/custom_components/meteocat/condition.py +63 -63
  24. package/custom_components/meteocat/config_flow.py +613 -613
  25. package/custom_components/meteocat/const.py +132 -132
  26. package/custom_components/meteocat/coordinator.py +248 -68
  27. package/custom_components/meteocat/helpers.py +58 -58
  28. package/custom_components/meteocat/manifest.json +25 -25
  29. package/custom_components/meteocat/options_flow.py +287 -287
  30. package/custom_components/meteocat/sensor.py +3 -1
  31. package/custom_components/meteocat/strings.json +1060 -1058
  32. package/custom_components/meteocat/translations/ca.json +1060 -1058
  33. package/custom_components/meteocat/translations/en.json +1060 -1058
  34. package/custom_components/meteocat/translations/es.json +1060 -1058
  35. package/custom_components/meteocat/version.py +1 -1
  36. package/custom_components/meteocat/weather.py +218 -218
  37. package/filetree.py +48 -48
  38. package/filetree.txt +80 -79
  39. package/hacs.json +8 -8
  40. package/info.md +11 -11
  41. package/package.json +22 -22
  42. package/poetry.lock +3222 -3222
  43. package/pyproject.toml +68 -68
  44. package/requirements.test.txt +3 -3
  45. package/setup.cfg +64 -64
  46. package/setup.py +10 -10
  47. package/tests/bandit.yaml +17 -17
  48. package/tests/conftest.py +19 -19
  49. package/tests/test_init.py +9 -9
@@ -1,45 +1,45 @@
1
- ---
2
- name: "🐞 Bug report"
3
- about: Report a problem with the integration
4
- title: "[Bug] "
5
- labels: bug
6
- assignees: ""
7
- ---
8
-
9
- ⚠️ **IMPORTANT:**
10
- - This template is **only** for reporting bugs, errors, or malfunctions.
11
- - Do **not** use it for improvements β†’ use the ♻️ Improvement request template.
12
- - Do **not** use it for new features or new API data β†’ use the πŸ†• New function template.
13
-
14
- ❌ The template is mandatory; failure to follow it will result in the issue being **closed without assistance**.
15
-
16
- Before opening a bug report, please search existing issues (including closed ones) and check the [Wiki - Troubleshooting](https://github.com/figorr/meteocat/wiki/Troubleshooting) page.
17
-
18
- ---
19
-
20
- ### Describe the bug
21
- <!-- A clear and concise description of what the bug is. -->
22
-
23
- ### To Reproduce
24
- <!-- Steps to reproduce the behavior. -->
25
- 1. Go to '...'
26
- 2. Click on '....'
27
- 3. Scroll down to '....'
28
- 4. See error
29
-
30
- ### Expected behavior
31
- <!-- A clear and concise description of what you expected to happen. -->
32
-
33
- ### Screenshots
34
- <!-- If applicable, add screenshots to help explain your problem. -->
35
-
36
- ### System details
37
- - Home Assistant version:
38
- - meteocat version (from `const.py` or HA startup log):
39
- - meteocatpy version (from `pip show meteocatpy` in the HA container or HA startup log):
40
-
41
- ### Debug Logs (meteocat & meteocatpy)
42
- <!-- Please provide [logs] - Enable debug logging for the component. -->
43
-
44
- ### Additional context
45
- <!-- Add any other context about the problem here. -->
1
+ ---
2
+ name: "🐞 Bug report"
3
+ about: Report a problem with the integration
4
+ title: "[Bug] "
5
+ labels: bug
6
+ assignees: ""
7
+ ---
8
+
9
+ ⚠️ **IMPORTANT:**
10
+ - This template is **only** for reporting bugs, errors, or malfunctions.
11
+ - Do **not** use it for improvements β†’ use the ♻️ Improvement request template.
12
+ - Do **not** use it for new features or new API data β†’ use the πŸ†• New function template.
13
+
14
+ ❌ The template is mandatory; failure to follow it will result in the issue being **closed without assistance**.
15
+
16
+ Before opening a bug report, please search existing issues (including closed ones) and check the [Wiki - Troubleshooting](https://github.com/figorr/meteocat/wiki/Troubleshooting) page.
17
+
18
+ ---
19
+
20
+ ### Describe the bug
21
+ <!-- A clear and concise description of what the bug is. -->
22
+
23
+ ### To Reproduce
24
+ <!-- Steps to reproduce the behavior. -->
25
+ 1. Go to '...'
26
+ 2. Click on '....'
27
+ 3. Scroll down to '....'
28
+ 4. See error
29
+
30
+ ### Expected behavior
31
+ <!-- A clear and concise description of what you expected to happen. -->
32
+
33
+ ### Screenshots
34
+ <!-- If applicable, add screenshots to help explain your problem. -->
35
+
36
+ ### System details
37
+ - Home Assistant version:
38
+ - meteocat version (from `const.py` or HA startup log):
39
+ - meteocatpy version (from `pip show meteocatpy` in the HA container or HA startup log):
40
+
41
+ ### Debug Logs (meteocat & meteocatpy)
42
+ <!-- Please provide [logs] - Enable debug logging for the component. -->
43
+
44
+ ### Additional context
45
+ <!-- Add any other context about the problem here. -->
@@ -1,8 +1,8 @@
1
- blank_issues_enabled: false
2
- contact_links:
3
- - name: πŸ“– Wiki - Troubleshooting
4
- url: https://github.com/figorr/meteocat/wiki/Troubleshooting
5
- about: Please check the Wiki before opening an issue.
6
- - name: πŸ’¬ Discussions
7
- url: https://github.com/figorr/meteocat/discussions
8
- about: Ask questions, share ideas, or get help from the community.
1
+ blank_issues_enabled: false
2
+ contact_links:
3
+ - name: πŸ“– Wiki - Troubleshooting
4
+ url: https://github.com/figorr/meteocat/wiki/Troubleshooting
5
+ about: Please check the Wiki before opening an issue.
6
+ - name: πŸ’¬ Discussions
7
+ url: https://github.com/figorr/meteocat/discussions
8
+ about: Ask questions, share ideas, or get help from the community.
@@ -1,39 +1,39 @@
1
- ---
2
- name: "♻️ Improvement request"
3
- about: Suggest an improvement or change to the current behavior of the integration
4
- title: "[Improvement] "
5
- labels: enhancement
6
- assignees: ""
7
- ---
8
-
9
- ⚠️ **NOTE:** This template is for improvements or changes to the **current behavior of the integration**.
10
-
11
- - It is **not** for bugs, errors, or malfunctions β†’ use the 🐞 Bug report template.
12
- - It is **not** for requesting new features or new API data β†’ use the πŸ†• New function template.
13
-
14
- ❌ Any request that does not follow these rules (e.g. bug reports or feature requests submitted here) will be **closed without assistance**.
15
-
16
- ---
17
-
18
- ### Current behavior
19
- <!-- Describe the current behavior of the integration. -->
20
-
21
- ### Expected behavior
22
- <!-- Describe what you would expect instead. -->
23
-
24
- ### Suggested solution
25
- <!-- If you have an idea of how it could be improved, describe it here. -->
26
-
27
- ### Alternatives considered
28
- <!-- Mention other approaches you thought about. -->
29
-
30
- ### Additional context
31
- <!-- Add any other context, screenshots, or examples related to your request. -->
32
-
33
- ---
34
-
35
- ### Checklist
36
- - [ ] I have searched existing issues (including closed ones).
37
- - [ ] I have checked the [Wiki](https://github.com/figorr/meteocat/wiki).
38
- - [ ] **I confirm this is not a bug or malfunction, but a request for improvement.**
39
- - [ ] This request is not a duplicate.
1
+ ---
2
+ name: "♻️ Improvement request"
3
+ about: Suggest an improvement or change to the current behavior of the integration
4
+ title: "[Improvement] "
5
+ labels: enhancement
6
+ assignees: ""
7
+ ---
8
+
9
+ ⚠️ **NOTE:** This template is for improvements or changes to the **current behavior of the integration**.
10
+
11
+ - It is **not** for bugs, errors, or malfunctions β†’ use the 🐞 Bug report template.
12
+ - It is **not** for requesting new features or new API data β†’ use the πŸ†• New function template.
13
+
14
+ ❌ Any request that does not follow these rules (e.g. bug reports or feature requests submitted here) will be **closed without assistance**.
15
+
16
+ ---
17
+
18
+ ### Current behavior
19
+ <!-- Describe the current behavior of the integration. -->
20
+
21
+ ### Expected behavior
22
+ <!-- Describe what you would expect instead. -->
23
+
24
+ ### Suggested solution
25
+ <!-- If you have an idea of how it could be improved, describe it here. -->
26
+
27
+ ### Alternatives considered
28
+ <!-- Mention other approaches you thought about. -->
29
+
30
+ ### Additional context
31
+ <!-- Add any other context, screenshots, or examples related to your request. -->
32
+
33
+ ---
34
+
35
+ ### Checklist
36
+ - [ ] I have searched existing issues (including closed ones).
37
+ - [ ] I have checked the [Wiki](https://github.com/figorr/meteocat/wiki).
38
+ - [ ] **I confirm this is not a bug or malfunction, but a request for improvement.**
39
+ - [ ] This request is not a duplicate.
@@ -1,41 +1,41 @@
1
- ---
2
- name: "πŸ†• New function (API-based)"
3
- about: Suggest a new function that uses data available from the Meteocat API
4
- title: "[Function] "
5
- labels: enhancement
6
- assignees: ""
7
- ---
8
-
9
- **IMPORTANT: Please check that the data you are requesting is available in the [Meteocat API Reference](https://apidocs.meteocat.gencat.cat/documentacio/).**
10
-
11
- ⚠️ **NOTE:** This template is for new functions or new API data for the **integration**.
12
-
13
- - It is **not** for bugs, errors, or malfunctions β†’ use the 🐞 Bug report template.
14
- - It is **not** for requesting improvements or changes to the current behavior of the integration β†’ use the ♻️ Improvement request template.
15
-
16
- ❌ Any request that does not follow these rules (e.g. bug reports or improvements requests submitted here) will be **closed without assistance**.
17
-
18
- ⚠️ **Note on API limits:** Each additional call to retrieve new or extra resources may cause the monthly API quota to be exhausted earlier than expected.
19
- Keep in mind that the available limits are relatively low, especially with the basic plan.
20
-
21
- ---
22
-
23
- ### Describe the function
24
- <!-- Clear and concise description of the new function you want to add. -->
25
-
26
- ### API endpoint / resource
27
- <!-- Indicate which API endpoint/resource provides this data. -->
28
-
29
- ### Why is it useful?
30
- <!-- Explain the value of this function for Home Assistant users. -->
31
-
32
- ### Additional context
33
- <!-- Add any other context, screenshots, or examples related to your request. -->
34
-
35
- ---
36
-
37
- ### Checklist
38
- - [ ] I have searched existing issues (including closed ones).
39
- - [ ] I have checked the [Wiki](https://github.com/figorr/meteocat/wiki).
40
- - [ ] **I have verified that the requested data is available in the [Meteocat API Reference](https://apidocs.meteocat.gencat.cat/documentacio/).**
41
- - [ ] This request is not a duplicate.
1
+ ---
2
+ name: "πŸ†• New function (API-based)"
3
+ about: Suggest a new function that uses data available from the Meteocat API
4
+ title: "[Function] "
5
+ labels: enhancement
6
+ assignees: ""
7
+ ---
8
+
9
+ **IMPORTANT: Please check that the data you are requesting is available in the [Meteocat API Reference](https://apidocs.meteocat.gencat.cat/documentacio/).**
10
+
11
+ ⚠️ **NOTE:** This template is for new functions or new API data for the **integration**.
12
+
13
+ - It is **not** for bugs, errors, or malfunctions β†’ use the 🐞 Bug report template.
14
+ - It is **not** for requesting improvements or changes to the current behavior of the integration β†’ use the ♻️ Improvement request template.
15
+
16
+ ❌ Any request that does not follow these rules (e.g. bug reports or improvements requests submitted here) will be **closed without assistance**.
17
+
18
+ ⚠️ **Note on API limits:** Each additional call to retrieve new or extra resources may cause the monthly API quota to be exhausted earlier than expected.
19
+ Keep in mind that the available limits are relatively low, especially with the basic plan.
20
+
21
+ ---
22
+
23
+ ### Describe the function
24
+ <!-- Clear and concise description of the new function you want to add. -->
25
+
26
+ ### API endpoint / resource
27
+ <!-- Indicate which API endpoint/resource provides this data. -->
28
+
29
+ ### Why is it useful?
30
+ <!-- Explain the value of this function for Home Assistant users. -->
31
+
32
+ ### Additional context
33
+ <!-- Add any other context, screenshots, or examples related to your request. -->
34
+
35
+ ---
36
+
37
+ ### Checklist
38
+ - [ ] I have searched existing issues (including closed ones).
39
+ - [ ] I have checked the [Wiki](https://github.com/figorr/meteocat/wiki).
40
+ - [ ] **I have verified that the requested data is available in the [Meteocat API Reference](https://apidocs.meteocat.gencat.cat/documentacio/).**
41
+ - [ ] This request is not a duplicate.
@@ -1,63 +1,63 @@
1
- - name: breaking-change
2
- color: d73a4a
3
- description: Indicates a breaking change affecting upgrade or usage.
4
-
5
- - name: bug
6
- color: d73a4a
7
- description: Something isn't working.
8
-
9
- - name: documentation
10
- color: 0075ca
11
- description: Improvements or additions to documentation.
12
-
13
- - name: duplicate
14
- color: cfd3d7
15
- description: This issue or pull request already exists.
16
-
17
- - name: enhancement
18
- color: a2eeef
19
- description: New feature or request.
20
-
21
- - name: first read
22
- color: 0052cc
23
- description: Mandatory reading before opening issues.
24
-
25
- - name: good first issue
26
- color: 7057ff
27
- description: Good for newcomers.
28
-
29
- - name: help wanted
30
- color: 008672
31
- description: Extra attention is needed.
32
-
33
- - name: invalid
34
- color: e4e669
35
- description: This doesn't seem right.
36
-
37
- - name: logs required
38
- color: b60205
39
- description: Logs are required.
40
-
41
- - name: merged
42
- color: b337b8
43
- description: Solution merged.
44
-
45
- - name: question
46
- color: d876e3
47
- description: Further information is requested.
48
-
49
- - name: solved
50
- color: 0e8a16
51
- description: Solved issue.
52
-
53
- - name: stale
54
- color: ededed
55
- description: Marked as stale due to inactivity.
56
-
57
- - name: wiki
58
- color: fbca04
59
- description: Documented at Wiki.
60
-
61
- - name: wontfix
62
- color: ffffff
63
- description: This will not be worked on.
1
+ - name: breaking-change
2
+ color: d73a4a
3
+ description: Indicates a breaking change affecting upgrade or usage.
4
+
5
+ - name: bug
6
+ color: d73a4a
7
+ description: Something isn't working.
8
+
9
+ - name: documentation
10
+ color: 0075ca
11
+ description: Improvements or additions to documentation.
12
+
13
+ - name: duplicate
14
+ color: cfd3d7
15
+ description: This issue or pull request already exists.
16
+
17
+ - name: enhancement
18
+ color: a2eeef
19
+ description: New feature or request.
20
+
21
+ - name: first read
22
+ color: 0052cc
23
+ description: Mandatory reading before opening issues.
24
+
25
+ - name: good first issue
26
+ color: 7057ff
27
+ description: Good for newcomers.
28
+
29
+ - name: help wanted
30
+ color: 008672
31
+ description: Extra attention is needed.
32
+
33
+ - name: invalid
34
+ color: e4e669
35
+ description: This doesn't seem right.
36
+
37
+ - name: logs required
38
+ color: b60205
39
+ description: Logs are required.
40
+
41
+ - name: merged
42
+ color: b337b8
43
+ description: Solution merged.
44
+
45
+ - name: question
46
+ color: d876e3
47
+ description: Further information is requested.
48
+
49
+ - name: solved
50
+ color: 0e8a16
51
+ description: Solved issue.
52
+
53
+ - name: stale
54
+ color: ededed
55
+ description: Marked as stale due to inactivity.
56
+
57
+ - name: wiki
58
+ color: fbca04
59
+ description: Documented at Wiki.
60
+
61
+ - name: wontfix
62
+ color: ffffff
63
+ description: This will not be worked on.
@@ -1,27 +1,27 @@
1
- name: Autocloser
2
-
3
- on:
4
- issues:
5
- types: [opened, edited, reopened]
6
-
7
- jobs:
8
- autoclose:
9
- runs-on: ubuntu-latest
10
- steps:
11
- - name: Autoclose issues that did not follow any template
12
- uses: roots/issue-closer@v1.1
13
- with:
14
- repo-token: ${{ secrets.GITHUB_TOKEN }}
15
- issue-close-message: >
16
- πŸ‘‹ @${{ github.event.issue.user.login }} this issue was automatically closed because it did not follow any of the required templates.
17
-
18
- ⚠️ Reminder:
19
- - Use the [🐞 Bug report template](https://github.com/figorr/meteocat/issues/new?template=bug_report.md) for errors or malfunctions.
20
- - Use the [♻️ Improvement request template](https://github.com/figorr/meteocat/issues/new?template=improvement.md) for changes to current behavior.
21
- - Use the [πŸ†• New function template](https://github.com/figorr/meteocat/issues/new?template=new_function.md) for API-based new features.
22
-
23
- The template is mandatory; failure to use it will result in issue closure.
24
- issue-pattern: >
25
- (### Describe the bug|### To Reproduce|### Expected behavior|### System details|### Debug Logs|
26
- I confirm this is not a bug or malfunction, but a request for improvement|
27
- I have verified that the requested data is available)
1
+ name: Autocloser
2
+
3
+ on:
4
+ issues:
5
+ types: [opened, edited, reopened]
6
+
7
+ jobs:
8
+ autoclose:
9
+ runs-on: ubuntu-latest
10
+ steps:
11
+ - name: Autoclose issues that did not follow any template
12
+ uses: roots/issue-closer@v1.1
13
+ with:
14
+ repo-token: ${{ secrets.GITHUB_TOKEN }}
15
+ issue-close-message: >
16
+ πŸ‘‹ @${{ github.event.issue.user.login }} this issue was automatically closed because it did not follow any of the required templates.
17
+
18
+ ⚠️ Reminder:
19
+ - Use the [🐞 Bug report template](https://github.com/figorr/meteocat/issues/new?template=bug_report.md) for errors or malfunctions.
20
+ - Use the [♻️ Improvement request template](https://github.com/figorr/meteocat/issues/new?template=improvement.md) for changes to current behavior.
21
+ - Use the [πŸ†• New function template](https://github.com/figorr/meteocat/issues/new?template=new_function.md) for API-based new features.
22
+
23
+ The template is mandatory; failure to use it will result in issue closure.
24
+ issue-pattern: >
25
+ (### Describe the bug|### To Reproduce|### Expected behavior|### System details|### Debug Logs|
26
+ I confirm this is not a bug or malfunction, but a request for improvement|
27
+ I have verified that the requested data is available)
@@ -1,48 +1,48 @@
1
- name: Close on labels
2
-
3
- on:
4
- issues:
5
- types:
6
- - labeled
7
-
8
- jobs:
9
- close-and-comment:
10
- runs-on: ubuntu-latest
11
- steps:
12
- - name: Filter relevant labels
13
- if: ${{ contains('wiki,solved,merged,duplicate', github.event.label.name) }}
14
- id: check
15
- run: echo "label=${{ github.event.label.name }}" >> $GITHUB_OUTPUT
16
-
17
- - name: Determine message based on label
18
- if: ${{ steps.check.outputs.label }}
19
- id: message
20
- run: |
21
- case "${{ github.event.label.name }}" in
22
- wiki)
23
- echo "message=πŸ‘‹ This issue is covered in the [Meteocat Wiki](https://github.com/figorr/meteocat/wiki). Please check the documentation there for guidance." >> $GITHUB_OUTPUT
24
- ;;
25
- solved)
26
- echo "message=βœ… This issue has been solved. Closing now." >> $GITHUB_OUTPUT
27
- ;;
28
- merged)
29
- echo "message=πŸ”€ This issue has been merged manually. 'Merged manually in master [commit_hash]'." >> $GITHUB_OUTPUT
30
- ;;
31
- duplicate)
32
- echo "message=πŸ“„ This issue is marked as a duplicate. 'Closed as duplicate of #<issue_number>'." >> $GITHUB_OUTPUT
33
- ;;
34
- esac
35
-
36
- - name: Add comment
37
- if: ${{ steps.check.outputs.label }}
38
- uses: peter-evans/create-or-update-comment@v4
39
- with:
40
- token: ${{ secrets.GITHUB_TOKEN }}
41
- issue-number: ${{ github.event.issue.number }}
42
- body: ${{ steps.message.outputs.message }}
43
-
44
- - name: Close issue if open
45
- if: ${{ github.event.issue.state == 'open' && steps.check.outputs.label }}
46
- uses: peter-evans/close-issue@v2
47
- with:
48
- issue-number: ${{ github.event.issue.number }}
1
+ name: Close on labels
2
+
3
+ on:
4
+ issues:
5
+ types:
6
+ - labeled
7
+
8
+ jobs:
9
+ close-and-comment:
10
+ runs-on: ubuntu-latest
11
+ steps:
12
+ - name: Filter relevant labels
13
+ if: ${{ contains('wiki,solved,merged,duplicate', github.event.label.name) }}
14
+ id: check
15
+ run: echo "label=${{ github.event.label.name }}" >> $GITHUB_OUTPUT
16
+
17
+ - name: Determine message based on label
18
+ if: ${{ steps.check.outputs.label }}
19
+ id: message
20
+ run: |
21
+ case "${{ github.event.label.name }}" in
22
+ wiki)
23
+ echo "message=πŸ‘‹ This issue is covered in the [Meteocat Wiki](https://github.com/figorr/meteocat/wiki). Please check the documentation there for guidance." >> $GITHUB_OUTPUT
24
+ ;;
25
+ solved)
26
+ echo "message=βœ… This issue has been solved. Closing now." >> $GITHUB_OUTPUT
27
+ ;;
28
+ merged)
29
+ echo "message=πŸ”€ This issue has been merged manually. 'Merged manually in master [commit_hash]'." >> $GITHUB_OUTPUT
30
+ ;;
31
+ duplicate)
32
+ echo "message=πŸ“„ This issue is marked as a duplicate. 'Closed as duplicate of #<issue_number>'." >> $GITHUB_OUTPUT
33
+ ;;
34
+ esac
35
+
36
+ - name: Add comment
37
+ if: ${{ steps.check.outputs.label }}
38
+ uses: peter-evans/create-or-update-comment@v4
39
+ with:
40
+ token: ${{ secrets.GITHUB_TOKEN }}
41
+ issue-number: ${{ github.event.issue.number }}
42
+ body: ${{ steps.message.outputs.message }}
43
+
44
+ - name: Close issue if open
45
+ if: ${{ github.event.issue.state == 'open' && steps.check.outputs.label }}
46
+ uses: peter-evans/close-issue@v2
47
+ with:
48
+ issue-number: ${{ github.event.issue.number }}
@@ -1,18 +1,18 @@
1
- name: Force sync labels
2
-
3
- on:
4
- workflow_dispatch: # solo se ejecuta manualmente
5
-
6
- jobs:
7
- labels:
8
- runs-on: ubuntu-latest
9
- steps:
10
- - uses: actions/checkout@v4
11
-
12
- - name: Force sync GitHub labels
13
- uses: crazy-max/ghaction-github-labeler@v5
14
- with:
15
- github-token: ${{ secrets.GITHUB_TOKEN }}
16
- yaml-file: .github/labels.yml
17
- skip-delete: false # elimina labels que no estΓ©n en el YAML
18
- dry-run: false # aplica cambios realmente
1
+ name: Force sync labels
2
+
3
+ on:
4
+ workflow_dispatch: # solo se ejecuta manualmente
5
+
6
+ jobs:
7
+ labels:
8
+ runs-on: ubuntu-latest
9
+ steps:
10
+ - uses: actions/checkout@v4
11
+
12
+ - name: Force sync GitHub labels
13
+ uses: crazy-max/ghaction-github-labeler@v5
14
+ with:
15
+ github-token: ${{ secrets.GITHUB_TOKEN }}
16
+ yaml-file: .github/labels.yml
17
+ skip-delete: false # elimina labels que no estΓ©n en el YAML
18
+ dry-run: false # aplica cambios realmente
@@ -1,14 +1,14 @@
1
- name: Validate with hassfest
2
-
3
- on:
4
- push:
5
- pull_request:
6
- schedule:
7
- - cron: "0 0 * * *"
8
-
9
- jobs:
10
- validate:
11
- runs-on: "ubuntu-latest"
12
- steps:
13
- - uses: "actions/checkout@v3"
1
+ name: Validate with hassfest
2
+
3
+ on:
4
+ push:
5
+ pull_request:
6
+ schedule:
7
+ - cron: "0 0 * * *"
8
+
9
+ jobs:
10
+ validate:
11
+ runs-on: "ubuntu-latest"
12
+ steps:
13
+ - uses: "actions/checkout@v3"
14
14
  - uses: home-assistant/actions/hassfest@master