Make galaxy.yml persistent and move out ansible.cfg #119
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Tompage1994
force-pushed
the
feature/persistent-galaxyyml
branch
from
c3560d4 to
03e223d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Makes galaxy.yml persistent and moves the template out of root. Also moves ansible.cfg from root.
This makes it installable from source
How should this be tested?
-develappended to the version that's just been released. We need to also be sure that the galaxy.yml of the released version is correctIs there a relevant Issue open for this?
related ansible/galaxy_collection#280
Other Relevant info, PRs, etc
Required redhat-cop/ansible_collections_tooling#33 to be merged