-
Notifications
You must be signed in to change notification settings - Fork 350
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
docs: Add more information about running integration tests #1278
docs: Add more information about running integration tests #1278
Conversation
Note that we'll probably want to copy-paste the same changes into community.aws. |
Note that I wasn't sure what type of change to put in the changelog. I couldn't see a docs option here. |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 09s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking the time to open this PR, new contributors are often some of the best folks to help with the 'getting started' docs.
I think these changes are a significant improvement. But I'd like some additional input from the others.
We often use
Not adding a changelog entry is one of the most common, easily fixable, issues we encounter during reviews, which is why there's now a test for it. The test could be more intelligent, but docs/test only PRs are relatively rare, and in the case of non-module plugins (inventory plugins, lookup plugins, etc), the docs fragments are actually parsed and used to automatically configure the |
Docs Build 📝Thank you for contribution!✨ This PR has been merged and your docs changes will be incorporated when they are next published. |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 5m 10s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a significant improvement to CONTRIBUTING.md, thankyou for taking the time. My only remaining concern is making sure that the README.md change doesn't break something.
If you're not comfortable making the extra-docs.yml
/ docs/docsite/rst
changes what we could do is remove the README.md change from this PR so we can get it merged and I'll line up something to tweak README.md and the other docsite changes.
I feel like linking from the README to CONTRIBUTING is one of the most important changes in this PR. I didn't even notice that the file CONTRIBUTING.md existed when I was trying to figure out how to contribute. I've tried to make those changes now. I don't know whether the fact that this is |
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 31s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, looks like your original idea of linking direct to CONTRIBUTING.md is what we'll have to go with for now. Many thanks for these changes.
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 12s |
@alinabuzachis I think these changes are very positive, any objections to merging them? |
Thanks @mdavis-xyz |
Build succeeded (gate pipeline). ✔️ ansible-galaxy-importer SUCCESS in 4m 14s |
SUMMARY
Adds content to CONTRIBUTING.md,
and rearranges some red-herring links.
Fixes: #924
ISSUE TYPE
COMPONENT NAME
CONTRIBUTING.md
ADDITIONAL INFORMATION