centersl/ansible-docs
1
0
Fork 0
mirror of https://github.com/ansible/ansible-documentation.git synced 2026-03-26 13:18:58 +07:00
Code Issues Packages Projects Releases Wiki Activity

Update ticketing stubs (#2366)

Browse Source 
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
This commit is contained in:
Abhijeet Kasurde
2025-02-05 09:04:59 -08:00
committed by GitHub
parent fcdb006e0f
commit 465331af24
12 changed files with 67 additions and 75 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
hacking/ticket_stubs/README.md
View File

@@ -3,4 +3,4 @@ What's this?
This is a directory of common responses to save some typing when responding to GitHub tickets to avoid
some carpal tunnel syndrome events as Ansible maintainers deal with the ticket influx.
They are present in the project Git repo (on GitHub) so it's easy for people to share and update these snippets of text.
They are present in the project git repo (on GitHub) so it's easy for people to share and update these snippets of text.

10
hacking/ticket_stubs/bug_internal_api.md
View File

@@ -9,15 +9,15 @@ as such this is not considered a bug unless it causes an issue with Ansible comm
(`ansible`, `ansible-playbook`, `ansible-doc`, etc).
We do support the provided API for use in developing plugins (modules, dynamic inventories, callbacks, strategies, etc),
but this does not seem to match that case.
but this does not match that case.
If you really need a stable API target to use Ansible, consider using ansible-runner:
If you need a stable API target to use Ansible, consider using ansible-runner:
* https://github.com/ansible/ansible-runner
* <https://github.com/ansible/ansible-runner>
Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below:
If you or anyone else has any further questions, please let us know by using any of the methods listed on the communication page:
* https://docs.ansible.com/ansible/latest/community/communication.html
* <https://docs.ansible.com/ansible/latest/community/communication.html>
Thank you once again for this and your interest in Ansible!

25
hacking/ticket_stubs/bug_wrong_repo.md
View File

@@ -8,31 +8,28 @@ This appears to be something that should be filed against another project or bug
<< CHOOSE AS APPROPRIATE >>
* https://github.com/ansible-community/ansible-lint
* https://github.com/ansible/ansible-runner
* https://github.com/ansible/ansible-navigator
* https://github.com/ansible-community/antsibull
* https://github.com/ansible-community/ara
* https://github.com/ansible/awx
* https://github.com/ansible-collections/community.general
* https://github.com/ansible-community/molecule
* For AAP or Tower licensees report issues via your Red Hat representative or https://issues.redhat.com
* <https://github.com/ansible/ansible-lint>
* <https://github.com/ansible/ansible-runner>
* <https://github.com/ansible/ansible-navigator>
* <https://github.com/ansible-community/antsibull>
* <https://github.com/ansible-community/ara>
* <https://github.com/ansible/awx>
* <https://github.com/ansible-collections/community.general>
* <https://github.com/ansible-community/molecule>
* For AAP Customer issues please see <https://docs.ansible.com/ansible/latest/community/communication.html#ansible-automation-platform-support-questions>
If you can stop by the tracker or forum for one of those projects, we'd appreciate it.
Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
Should you still wish to discuss things further, or if you disagree with our thought process, please stop by one of our two mailing lists:
* https://groups.google.com/forum/#!forum/ansible-devel
* [ansible-core on the Ansible Forum](https://forum.ansible.com/tag/ansible-core)
* Matrix: [#devel:ansible.im](https://matrix.to/#/#devel:ansible.im)
* IRC: #ansible-devel on [irc.libera.chat](https://libera.chat/)
We'd be happy to discuss things.
See this page for a complete list of communication channels and their purposes:
* https://docs.ansible.com/ansible/latest/community/communication.html
* <https://docs.ansible.com/ansible/latest/community/communication.html>
Thank you once again!

11
hacking/ticket_stubs/collections.md
View File

@@ -2,15 +2,16 @@ Hi!
Thank you very much for your submission to Ansible. It means a lot to us that you've taken the time to contribute.
Since Ansible 2.10 we are no longer accepting new modules/plugins into Ansible Core. However, we recommend looking into providing this functionality through Ansible Galaxy via Ansible Collections. You can find more information about collections at:
Since Ansible 2.10 we are no longer accepting new modules/plugins into Ansible core.
However, we recommend looking into providing this functionality through Ansible Galaxy via Ansible Collections. You can find more information about collections at:
* https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html.
* <https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html>.
Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved.
The Ansible Forum is the best place to start a discussion about this particular issue.
See this page for a complete and up to date list of communication channels and their purposes:
See this page for a complete and up-to-date list of communication channels and their purposes:
* https://docs.ansible.com/ansible/latest/community/communication.html
* <https://docs.ansible.com/ansible/latest/community/communication.html>
Thank you once again for this and your interest in Ansible!

12
hacking/ticket_stubs/guide_newbie_about_gh_and_contributing_to_ansible.md
View File

@@ -1,21 +1,21 @@
@{{ paste.handle.here }} it seems to me that you are new to GitHub and
@{{ paste.handle.here }} It seems to me that you are new to GitHub and
have created this
[PR](https://help.github.com/articles/about-pull-requests/)
accidentally. That's why I'm closing it.
But no worries! Welcome to the Ansible community :)
Assuming that you wanted to create actual contribution, I think that
Assuming that you wanted to create an actual contribution, I think that
you may want to learn and read through the following articles I've
gathered for you:
• https://opensource.guide/how-to-contribute/
• https://docs.ansible.com/ansible/devel/community/
• <https://opensource.guide/how-to-contribute/>
• <https://docs.ansible.com/ansible/devel/community/>
Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below:
If you or anyone else has any further questions, please let us know by using any of the communication methods listed on the page below:
https://docs.ansible.com/ansible/latest/community/communication.html
<https://docs.ansible.com/ansible/latest/community/communication.html>
Have a nice day!

12
hacking/ticket_stubs/no_thanks.md
View File

@@ -1,19 +1,19 @@
Hi!
Thanks very much for your submission to Ansible. It means a lot to us that you've taken time to contribute.
Thanks very much for your submission to Ansible. It means a lot to us that you've taken the time to contribute.
Unfortunately, we're not sure if we want this feature in the program, and I don't want this to seem confrontational.
Our reasons for this are:
* (A) INSERT ITEM HERE
However, we're absolutely always up for discussion.
However, we're always up for discussion.
Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below:
If you or anyone else has any further questions, please let us know by using any of the communication methods listed on the page below:
* https://docs.ansible.com/ansible/latest/community/communication.html
* <https://docs.ansible.com/ansible/latest/community/communication.html>
In the future, sometimes starting a discussion on the development list prior to implementing a feature can make getting things included a little easier, but it's not always necessary.
In the future, sometimes starting a discussion on the Ansible Forum before implementing
a feature can make getting things included a little easier, but it's not always necessary.
Thank you once again for this and your interest in Ansible!

11
hacking/ticket_stubs/pr_duplicate.md
View File

@@ -1,6 +1,6 @@
Hi!
Thanks very much for your submission to Ansible. It means a lot to us that you've taken time to contribute.
Thanks very much for your submission to Ansible. It means a lot to us that you've taken the time to contribute.
It looks like the work from this pull request is a duplicate of the following PR(s):
@@ -8,14 +8,13 @@ It looks like the work from this pull request is a duplicate of the following PR
Based on this, we are going to close this PR in favor of the above as a consolidated location to keep track of the issue.
However, we're absolutely always up for discussion.
In the future, sometimes starting a discussion on the development list prior to implementing a feature
However, we're always up for discussion.
In the future, sometimes starting a discussion on the Ansible Forum before implementing a feature
can make getting things included a little easier, but it's not always necessary.
Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below:
If you or anyone else has any further questions, please let us know by using any of the communication methods listed on the page below:
* https://docs.ansible.com/ansible/latest/community/communication.html
* <https://docs.ansible.com/ansible/latest/community/communication.html>
Thank you once again for this and your interest in Ansible!

8
hacking/ticket_stubs/pr_merged.md
View File

@@ -1,15 +1,15 @@
Hi!
This has been merged in, and will also be included in the next major release.
For more info on our process see https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html#ansible-core-workflow
For more info on our process see <https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html#ansible-core-workflow>
If you or anyone else has any further questions, please let us know by stopping by one of the mailing lists or chat channels, as appropriate.
Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved.
The Ansible Forum is the best place to start a discussion about this particular issue.
See this page for a complete and up to date list of communication channels and their purposes:
See this page for a complete and up-to-date list of communication channels and their purposes:
* https://docs.ansible.com/ansible/latest/community/communication.html
* <https://docs.ansible.com/ansible/latest/community/communication.html>
Thank you!

10
hacking/ticket_stubs/proposal.md
View File

@@ -3,17 +3,15 @@ Hi!
Ansible has a Proposal process for large feature ideas or changes in current design and functionality, such as this.
If you are still interested in seeing this new feature get into Ansible, please submit a proposal for it using this process.
https://github.com/ansible/proposals/blob/master/proposals_process_proposal.md
<https://github.com/ansible/proposals/blob/master/proposals_process_proposal.md>
Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved.
* #ansible-devel on [irc.libera.chat](https://libera.chat/)
* https://groups.google.com/forum/#!forum/ansible-devel
The Ansible Forum is the best place to start a discussion about this particular issue.
* <https://forum.ansible.com/tag/ansible-core>
Or check this page for a more complete list of communication channels and their purposes:
* https://docs.ansible.com/ansible/latest/community/communication.html
* <https://docs.ansible.com/ansible/latest/community/communication.html>
Thank you!

14
hacking/ticket_stubs/question_not_bug.md
View File

@@ -2,18 +2,18 @@ Hi!
Thanks very much for your interest in Ansible. It means a lot to us.
This appears to be a user question, and we'd like to direct these kinds of things to either the mailing list or the IRC channel.
This appears to be a user question, and we'd like to direct this topic to the Ansible Forum.
* IRC: #ansible on [irc.libera.chat](https://libera.chat/)
* mailing list: https://groups.google.com/forum/#!forum/ansible-project
* [Ansible Forum](https://forum.ansible.com)
See this page for a complete and up to date list of communication channels and their purposes:
See this page for a complete and up-to-date list of communication channels and their purposes:
* https://docs.ansible.com/ansible/latest/community/communication.html
* <https://docs.ansible.com/ansible/latest/community/communication.html>
Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
If don't you think this particular issue is resolved, you should still stop by there first, we'd appreciate it.
If you don't think this particular issue is resolved, you should still stop by there first, we'd appreciate it.
This allows us to keep the issue tracker for bugs, pull requests, RFEs and the like.
Thank you once again and we look forward to seeing you on the list or IRC. Thanks!
Thank you once again, and we look forward to seeing you on the Ansible Forum!
Thanks!

6
hacking/ticket_stubs/resolved.md
View File

@@ -4,13 +4,13 @@ We have ascertained that the following PR/commits should resolve this question o
<< INSERT SHA/PR LINK HERE >>
This should be included newer releases starting with << RELEASE/the next [major] release(s) >>.
This is included in newer releases starting with << RELEASE/the next [major] release(s) >>.
Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
The mailing list and irc are great ways to ask questions, or post if you don't think this particular issue is resolved.
The Ansible Forum is the best place to start a discussion about this particular issue.
See this page for a complete list of communication channels and their purposes:
* https://docs.ansible.com/ansible/latest/community/communication.html
* <https://docs.ansible.com/ansible/latest/community/communication.html>
Thank you!

9
hacking/ticket_stubs/wider_discussion.md
View File

@@ -8,15 +8,12 @@ Reasons for this include:
* INSERT REASONS!
Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
Can you please post on ansible-development list so we can talk about this idea with the wider group?
Please post your idea on the Ansible Forum so we can discuss it with the wider group.
* https://groups.google.com/forum/#!forum/ansible-devel
* Matrix: [#devel:ansible.im](https://matrix.to/#/#devel:ansible.im)
* #ansible-devel on [irc.libera.chat](https://libera.chat/)
* [Ansible Core on the Ansible Forum](https://forum.ansible.com/tag/ansible-core)
For other alternatives, check this page for a more complete list of communication channels and their purposes:
* https://docs.ansible.com/ansible/latest/community/communication.html
* <https://docs.ansible.com/ansible/latest/community/communication.html>
Thank you once again for this and your interest in Ansible!