Closed dafyddj closed 10 months ago
[build]
[chore]
[ci]
[feat]
[fix]
[perf]
[refactor]
[revert]
[style]
[docs]
[test]
BREAKING CHANGE
No.
Switch to using pre-commit's built-in file filtering (a long needed change)
pre-commit
yamllint
test/
ignore
Tested by comparing a list files that yamllint checks using --list-files before and after the change
--list-files
README
Available states
pillar.example
state_top
:tada: This PR is included in version 5.0.10 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?No.
Related issues and/or pull requests
Describe the changes you're proposing
Switch to using
pre-commit
's built-in file filtering (a long needed change)yamllint
when relevant files have changedyamllint
bug whereby pillar files undertest/
were not checked due to a conflictingignore
entryTested by comparing a list files that
yamllint
checks using--list-files
before and after the changePillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context