|
|
|
@ -52,7 +52,7 @@ Get Involved
|
|
|
|
|
* Submit a proposed code update through a pull request to the ``devel`` branch.
|
|
|
|
|
* Talk to us before making larger changes
|
|
|
|
|
to avoid duplicate efforts. This not only helps everyone
|
|
|
|
|
know what is going on, it also helps save time and effort if we decide
|
|
|
|
|
know what is going on, but it also helps save time and effort if we decide
|
|
|
|
|
some changes are needed.
|
|
|
|
|
* For a list of email lists, IRC channels and Working Groups, see the
|
|
|
|
|
`Communication page <https://docs.ansible.com/ansible/latest/community/communication.html>`_
|
|
|
|
@ -63,7 +63,7 @@ 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>`_
|
|
|
|
|
* `Conventions, tips, and pitfalls <https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_best_practices.html>`_
|
|
|
|
|
|
|
|
|
|
Branch Info
|
|
|
|
|
===========
|
|
|
|
|