summaryrefslogtreecommitdiffstats
path: root/hacking/ticket_stubs/pr_duplicate.md
diff options
context:
space:
mode:
authorAbhijeet Kasurde <akasurde@redhat.com>2025-01-13 21:04:50 +0100
committerGitHub <noreply@github.com>2025-01-13 21:04:50 +0100
commit508c4dc93ee8dcad4addf20ecb385f1496ebc5fe (patch)
treef8b4ff4bfdd4365d182d075715b95bf31e09d253 /hacking/ticket_stubs/pr_duplicate.md
parentBump acme test container to 2.3.0 (#84547) (diff)
downloadansible-508c4dc93ee8dcad4addf20ecb385f1496ebc5fe.tar.xz
ansible-508c4dc93ee8dcad4addf20ecb385f1496ebc5fe.zip
Update ticketing stubs (#84535)
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
Diffstat (limited to 'hacking/ticket_stubs/pr_duplicate.md')
-rw-r--r--hacking/ticket_stubs/pr_duplicate.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/hacking/ticket_stubs/pr_duplicate.md b/hacking/ticket_stubs/pr_duplicate.md
index 080e4e4abf..7bc88bc273 100644
--- a/hacking/ticket_stubs/pr_duplicate.md
+++ b/hacking/ticket_stubs/pr_duplicate.md
@@ -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>