Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build-release: Improve galaxy-requirements.yaml generation #350

Merged
merged 1 commit into from
Dec 2, 2021

Conversation

dmsimard
Copy link
Contributor

@dmsimard dmsimard commented Dec 2, 2021

  • Collections must be nested under "collections:"
  • Include source to ensure collections and their dependencies are
    retrieved from galaxy.ansible.com
  • Rename it galaxy-requirements.yaml and include it in
    ansible-build-data

@dmsimard dmsimard force-pushed the galaxy-requirements branch from 794aac8 to 590b2be Compare December 2, 2021 18:23
- Collections must be nested under "collections:"
- Include source to ensure collections and their dependencies are
  retrieved from galaxy.ansible.com
- Rename it galaxy-requirements.yaml and include it in
  ansible-build-data
@dmsimard dmsimard force-pushed the galaxy-requirements branch from 590b2be to a8cb176 Compare December 2, 2021 18:25
@felixfontein felixfontein merged commit ab1d25a into ansible-community:main Dec 2, 2021
@felixfontein
Copy link
Collaborator

@dmsimard thanks for improving this!

@dmsimard
Copy link
Contributor Author

dmsimard commented Dec 2, 2021

and thank you @felixfontein for reviewing :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants