-
Notifications
You must be signed in to change notification settings - Fork 133
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
galaxy_collection folder #1933
galaxy_collection folder #1933
Conversation
Can one of the admins verify this patch? |
@oraNod can you help with this, I would love to get this out of the way |
e000224
to
87ff29e
Compare
@Dule-martins - thanks for your patience here as we work through an unfamiliar workflow. The CI is now failing because of : Looking at the Contributor guide It looks like we can avoid adding a changelog here if you amend the commit message to use |
Thank you @samccann I will take a look at it again and again until I succeed at it! Thanks for replying |
Partial-Issue: AAH-2420
Hello @samccann As you can see I tried to follow your instructions but we still have a failed Galaxy CI. I went through the error log and found out that the After going through the contributors' guide I noticed that a commit that references one or multiple issues must have a change log. In our case how can I identify the change log so I could add it to the commit message since that is what is missing? |
HEy, either you put echo "add skeleton for galaxy_collection docs" > CHANGES/2420.doc |
Issue: AAH-2420
What is this PR doing:
This PR resolves the issue with number #318 found in the ansible-community / community-team repo
Issue: AAH-2420
Reviewers must know:
PR Author & Reviewers: Keep or remove backport labels per Backporting Guidelines
Reviewers: Look for sound code, no code smells, docs & test coverage
Merger: When merging, include the Jira issue link in the squashed commit