Move coding guidelines links to readme. (#68479)

CODING_GUIDELINES.md

@@ -1,10 +0,0 @@
-Coding Guidelines
-=================
-
-Hi! Thanks for your interest in contributing to Ansible. We document our Coding Guidelines in the [Developer Guide](https://docs.ansible.com/ansible/devel/dev_guide/). We particularly suggest you review:
-
-* [Contributing your module to Ansible](https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_checklist.html)
-
-* [Development conventions, tips and pitfalls](https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_best_practices.html)
-
-Our [Community Guide](https://docs.ansible.com/ansible/devel/community/) may also help you connect with the community of Ansible developers.

README.rst

@@ -58,6 +58,14 @@ Get Involved
 *  For a list of email lists, IRC channels and Working Groups, see the
    `Communication page <https://docs.ansible.com/ansible/latest/community/communication.html>`_
 
+Coding Guidelines
+=================
+
+We document our Coding Guidelines in the `Developer Guide <https://docs.ansible.com/ansible/devel/dev_guide/>`_. We particularly suggest you review:
+
+* `Contributing your module to Ansible <https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_checklist.html>`_
+* `Conventions, tips and pitfalls <https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_best_practices.html>`_
+
 Branch Info
 ===========
 

test/sanity/code-smell/package-data.py

@@ -62,7 +62,6 @@ def assemble_files_to_ship(complete_file_list):
         'examples/plugin_filters.yml',
         'hacking/env-setup',
         'hacking/env-setup.fish',
-        'CODING_GUIDELINES.md',
         'MANIFEST',
     ))