@dafyddj After our discussion earlier on Slack, I'd prefer to keep the filenames in sync. I've got the ssf-formula working for Linux testing and those are currently producing .github/workflows/kitchen.yml -- I don't want anything to happen to these files inadvertently.
Pillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
[ ] Updated the README (e.g. Available states).
[ ] Updated pillar.example.
Testing checklist
[ ] Included in Kitchen (i.e. under state_top).
[ ] Covered by new/existing tests (e.g. InSpec, Serverspec, etc.).
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
Re: Preparation for introducing Linux testing in GitHub Actions (for select formulas). Also: https://github.com/saltstack-formulas/openvpn-formula/pull/142
@dafyddj After our discussion earlier on Slack, I'd prefer to keep the filenames in sync. I've got the
ssf-formula
working for Linux testing and those are currently producing.github/workflows/kitchen.yml
-- I don't want anything to happen to these files inadvertently.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