Closed myii closed 5 years ago
[build]
[chore]
[ci]
[feat]
[fix]
[perf]
[refactor]
[revert]
[style]
[docs]
[test]
BREAKING CHANGE
No.
Follows on from #171.
Introduce a pre-salted FreeBSD Vagrant box for local testing, using:
$ INSTANCE=freebsd-120-2019-2-py3 \ && export KITCHEN_LOCAL_YAML=kitchen.vagrant.yml $ bin/kitchen verify ${INSTANCE}
This Vagrant box has been kindly prepared (and provided) by @krionbsd.
README
Available states
pillar.example
state_top
merged it.
Thanks.
:tada: This PR is included in version 0.43.0 :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
Follows on from #171.
Describe the changes you're proposing
Introduce a pre-salted FreeBSD Vagrant box for local testing, using:
This Vagrant box has been kindly prepared (and provided) by @krionbsd.
Pillar / 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