Closed myii closed 4 years ago
[build]
[chore]
[ci]
[feat]
[fix]
[perf]
[refactor]
[revert]
[style]
[docs]
[test]
BREAKING CHANGE
No.
Realised that there was an erroneous entry in osfingermap.yaml here:
osfingermap.yaml
Added the rest of the OS details from our current supported CI platforms, to prevent having to look up the values each time from elsewhere.
As-is.
N/a.
README
Available states
pillar.example
state_top
@baby-gnu @aboe76 Thanks for the reviews.
:tada: This PR is included in version 4.0.3 :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
Realised that there was an erroneous entry in
osfingermap.yaml
here:Added the rest of the OS details from our current supported CI platforms, to prevent having to look up the values each time from elsewhere.
Pillar / config required to test the proposed changes
As-is.
Debug log showing how the proposed changes work
N/a.
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context