OSSForks/ansible
1
0
Fork 0
mirror of https://github.com/zebrajr/ansible.git synced 2025-12-06 00:19:48 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update ticketing stubs (#84535)

Browse Source 
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
This commit is contained in:
Abhijeet Kasurde 2025-01-13 12:04:50 -08:00 committed by GitHub
parent 60e2135c2b
commit 508c4dc93e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
10 changed files with 29 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
hacking/ticket_stubs/bug_internal_api.md
View File

@ -9,14 +9,14 @@ 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>
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>

4
hacking/ticket_stubs/collections.md
View File

@ -8,9 +8,9 @@ However, we recommend looking into providing this functionality through Ansible
* <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>

6
hacking/ticket_stubs/guide_newbie_about_gh_and_contributing_to_ansible.md
View File

@ -1,11 +1,11 @@
@{{ 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:
@ -14,7 +14,7 @@ gathered for you:
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>

8
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>
In the future, sometimes starting a discussion on the development list prior to implementing
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!

8
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,12 +8,12 @@ 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>

4
hacking/ticket_stubs/pr_merged.md
View File

@ -6,9 +6,9 @@ For more info on our process see <https://docs.ansible.com/ansible/devel/referen
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>

2
hacking/ticket_stubs/proposal.md
View File

@ -6,7 +6,7 @@ If you are still interested in seeing this new feature get into Ansible, please
<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 Forum is the best 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.
* <https://forum.ansible.com/tag/ansible-core>

10
hacking/ticket_stubs/question_not_bug.md
View File

@ -2,16 +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 topic to the Ansible Forum.
This appears to be a user question, and we'd like to direct this topic to the Ansible Forum.
* [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>
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!

4
hacking/ticket_stubs/resolved.md
View File

@ -4,10 +4,10 @@ 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:

5
hacking/ticket_stubs/wider_discussion.md
View File

@ -1,6 +1,6 @@
Hi!
Thanks very much for your submission to Ansible. It means a lot to us.
Thanks very much for your submission to Ansible. It means a lot to us.
We are interested in this idea and would like to see a wider discussion on it on one of our lists.
Reasons for this include:
@ -8,10 +8,9 @@ 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 Ansible Forum 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.
* [Ansible Core on the Ansible Forum](https://forum.ansible.com/tag/ansible-core)
* Matrix: [#devel:ansible.im](https://matrix.to/#/#devel:ansible.im)
For other alternatives, check this page for a more complete list of communication channels and their purposes: