ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Add a doc reference to the module developer guide. (#18658)

Browse source 
Addresses https://github.com/ansible/ansible-modules-core/issues/5672
This commit is contained in:
jctanner 2016-11-28 21:26:14 -05:00 committed by scottb
parent 57f4a9885e
commit 4d78c784a6
1 changed files with 3 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
docsite/rst/community.rst
View file

@ -147,6 +147,9 @@ Note that we do keep Ansible to a particular aesthetic, so if you are unclear ab
is a good fit or not, having the discussion on the development list is often a lot easier than having is a good fit or not, having the discussion on the development list is often a lot easier than having
to modify a pull request later. to modify a pull request later.
New module developers should read through `http://docs.ansible.com/ansible/dev_guide/developing_modules.html`_ for helpful pointers
and information about running adhoc tests `http://docs.ansible.com/ansible/dev_guide/developing_modules.html#testing-modules`_.
When submitting patches, be sure to run the unit tests first ``make tests`` and always use, these are the same basic When submitting patches, be sure to run the unit tests first ``make tests`` and always use, these are the same basic
tests that will automatically run on Shippable when creating the PR. There are more in depth tests in the ``tests/integration`` tests that will automatically run on Shippable when creating the PR. There are more in depth tests in the ``tests/integration``
directory, classified as destructive and non_destructive, run these if they pertain to your modification. They are set up directory, classified as destructive and non_destructive, run these if they pertain to your modification. They are set up