Feature/persistent galaxyyml #33
Merged
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
This was referenced Aug 2, 2023
sean-m-sullivan
approved these changes
Aug 2, 2023
|
ok, sounds good, I know I was back and forth on it, but this is simple enough change as well. |
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?
Changes the changelog pipeline to also persist the galaxy.yml (which it will already if the .gitignore isn't set in the collection repos). But it will also append
-develonto the version so that when installing from source you will have a different version than has been releasedHow should this be tested?
Merge, then run the CI release on the real collections.
Is there a relevant Issue open for this?
related ansible/galaxy_collection#280
Other Relevant info, PRs, etc