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

README: Add Communication section with Forum information #380

Merged
merged 1 commit into from
Aug 8, 2024

Conversation

Andersson007
Copy link
Contributor

SUMMARY

Dear maintainers,
As a part of the Consolidating Ansible discussion platforms initiative, this PR adds the communication section template defined by the community to the README. Similar PRs are being raised across all included collections under the ansible-collection org for now.

  • If you have your forum group and/or tags related to the collection, please update corresponding lines by suggesting changes to the PR.
  • If the collection is not present on the Ansible forum yet, please check out the existing tags and groups - use what suits your collection. If there is no appropritate tag and group yet, please request one. Then update corresponding lines by suggesting changes to the PR.
  • Presence in the forum will soon likely become a part of the Collection inclusion requirements.
ISSUE TYPE
  • Docs Pull Request
COMPONENT NAME

README.md

@Andersson007
Copy link
Contributor Author

The CI failures are unrelated to the PR, ready for review

Copy link
Collaborator

@mamercad mamercad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚢

@mamercad mamercad merged commit 488e3cf into ansible-collections:main Aug 8, 2024
8 of 10 checks passed
@Andersson007
Copy link
Contributor Author

@mamercad hello, thanks for merging but: the following points in the PR had had to be addressed before merging:)

But you can do it yourself in another PR, no problem

@mamercad mamercad mentioned this pull request Aug 9, 2024
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