Closed stasjok closed 2 years ago
:tada: This PR is included in version 5.0.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Unlike the other fixes pushed out using https://github.com/myii/ssf-formula/pull/418, I realised that we're not managing docs/map.jinja.rst
with the ssf-formula
. @baby-gnu Did I mention something at the time, to explain why this isn't managed?
Unlike the other fixes pushed out using myii/ssf-formula#418, I realised that we're not managing
docs/map.jinja.rst
with thessf-formula
. @baby-gnu Did I mention something at the time, to explain why this isn't managed?
Not that I remember. I see no reason not to manage it.
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
Based on source code
post-map.jinja
path is incorrect in docs, right?https://github.com/saltstack-formulas/template-formula/blob/080fdcd9f136f19d2a7dd15b17bf4de5c1c4a3c8/TEMPLATE/map.jinja#L66
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