Open vveliev opened 2 years ago
[build]
[chore]
[ci]
[feat]
[fix]
[perf]
[refactor]
[revert]
[style]
[docs]
[test]
BREAKING CHANGE
No.
updating python git package name for Debian 11
When working with gitfs current configuration failing for state salt.gitfs.pygit2 as it's not able to find default package name.
salt.gitfs.pygit2
default.
salt-call state.sls salt.gitfs.pygit2
README
Available states
pillar.example
state_top
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
updating python git package name for Debian 11
When working with gitfs current configuration failing for state
salt.gitfs.pygit2
as it's not able to find default package name.Pillar / config required to test the proposed changes
default.
Debug log showing how the proposed changes work
salt-call state.sls salt.gitfs.pygit2
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context