-
Notifications
You must be signed in to change notification settings - Fork 403
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
Document how to run integration tests more clearly #1607
Labels
Comments
Files identified in the description: If these files are inaccurate, please update the |
tremble
added a commit
to tremble/community.aws
that referenced
this issue
Feb 8, 2023
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Feb 22, 2023
Update contributing to sync with amazon.aws Fixes: #1607 SUMMARY Update CONTRIBUTING.md to sync with amazon.aws and pick up various recent improvements (See also ansible-collections/amazon.aws#924) ISSUE TYPE Docs Pull Request COMPONENT NAME CONTRIBUTING.md ADDITIONAL INFORMATION Reviewed-by: Alina Buzachis
kamilturek
pushed a commit
to kamilturek/community.aws
that referenced
this issue
Mar 19, 2023
Update contributing to sync with amazon.aws Fixes: ansible-collections#1607 SUMMARY Update CONTRIBUTING.md to sync with amazon.aws and pick up various recent improvements (See also ansible-collections/amazon.aws#924) ISSUE TYPE Docs Pull Request COMPONENT NAME CONTRIBUTING.md ADDITIONAL INFORMATION Reviewed-by: Alina Buzachis
abikouo
pushed a commit
to abikouo/community.aws
that referenced
this issue
Oct 24, 2023
…ags (ansible-collections#1813) s3_object - fix NoSuchTagSet error when S3 endpoint doesn't support tags SUMMARY is_boto3_error_code only supports being passed a string or list. In the refactor of s3_object it was passed a tuple, so the errors weren't being cleanly caught. ISSUE TYPE Bugfix Pull Request COMPONENT NAME s3_object ADDITIONAL INFORMATION fixes: ansible-collections#1607 Reviewed-by: Alina Buzachis
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
In amazon.aws we just merged this PR for this issue, to add more information to the contributing docs.
This repo has the same state as the other repo had before that PR. I think we should apply the same changes.
We can either:
Which approach is preferable?
Issue Type
Documentation Report
Component Name
CONTRIBUTING.md
Ansible Version
$ ansible --version
Collection Versions
N/A
Configuration
N/A
OS / Environment
No response
Additional Information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: