ansible-readme.rst: change link to ansible-build-data tracker

ansible-community · Nov 21, 2023 · dbf83be · dbf83be
1 parent d13bbe7
commit dbf83be
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/src/antsibull/data/ansible-readme.rst b/src/antsibull/data/ansible-readme.rst
@@ -59,7 +59,7 @@ the `ansible-core issue tracker </~https://github.com/ansible/ansible/issues/>`_.
 Issues with the ``ansible`` package build process or serious bugs or
 vulnerabilities in a collection that are not addressed after opening an issue
 in the collection's issue tracker should be reported on
-`ansible-build-data's issue tracker </~https://github.com/ansible-community/ansible-build-data/issues>`_.
+`ansible-build-data's issue tracker </~https://github.com/ansible-community/ansible-build-data#issue-tracker>`_.
 
 Refer to the `Communication page
 <https://docs.ansible.com/ansible/latest/community/communication.html>`_ for a

diff --git a/tests/test_data/package-files/7.5.0/README.rst b/tests/test_data/package-files/7.5.0/README.rst
@@ -59,7 +59,7 @@ the `ansible-core issue tracker </~https://github.com/ansible/ansible/issues/>`_.
 Issues with the ``ansible`` package build process or serious bugs or
 vulnerabilities in a collection that are not addressed after opening an issue
 in the collection's issue tracker should be reported on
-`ansible-build-data's issue tracker </~https://github.com/ansible-community/ansible-build-data/issues>`_.
+`ansible-build-data's issue tracker </~https://github.com/ansible-community/ansible-build-data#issue-tracker>`_.
 
 Refer to the `Communication page
 <https://docs.ansible.com/ansible/latest/community/communication.html>`_ for a

diff --git a/tests/test_data/package-files/8.1.0/README.rst b/tests/test_data/package-files/8.1.0/README.rst
@@ -59,7 +59,7 @@ the `ansible-core issue tracker </~https://github.com/ansible/ansible/issues/>`_.
 Issues with the ``ansible`` package build process or serious bugs or
 vulnerabilities in a collection that are not addressed after opening an issue
 in the collection's issue tracker should be reported on
-`ansible-build-data's issue tracker </~https://github.com/ansible-community/ansible-build-data/issues>`_.
+`ansible-build-data's issue tracker </~https://github.com/ansible-community/ansible-build-data#issue-tracker>`_.
 
 Refer to the `Communication page
 <https://docs.ansible.com/ansible/latest/community/communication.html>`_ for a

diff --git a/tests/test_data/package-files/force_setup_cfg/8.1.0/README.rst b/tests/test_data/package-files/force_setup_cfg/8.1.0/README.rst
@@ -59,7 +59,7 @@ the `ansible-core issue tracker </~https://github.com/ansible/ansible/issues/>`_.
 Issues with the ``ansible`` package build process or serious bugs or
 vulnerabilities in a collection that are not addressed after opening an issue
 in the collection's issue tracker should be reported on
-`ansible-build-data's issue tracker </~https://github.com/ansible-community/ansible-build-data/issues>`_.
+`ansible-build-data's issue tracker </~https://github.com/ansible-community/ansible-build-data#issue-tracker>`_.
 
 Refer to the `Communication page
 <https://docs.ansible.com/ansible/latest/community/communication.html>`_ for a