wbrawner/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ansible/CODING_GUIDELINES.md

11 lines
645 B
Markdown
Raw Normal View History

Add the start of a coding guidelines document.
2014-01-26 21:42:21 +00:00
Coding Guidelines
=================
[stable-2.7] bulk docs update (#47828) * Document all Working Group, email lists and IRC channels (#47615) (cherry picked from commit 749af9fd2200e9895555734d9adac84c13275387) * Docs: No need to follow up on backport PRs (#47616) (cherry picked from commit 166e84b9c4fe63dd5ec4cec5f2dad5b24b9bc26e) * Tidy up Contributors Docs (#47619) (cherry picked from commit 72359a10e6cc0bef16b8742dd76355f0f1816dfe) * Correct AWX community link (#47742) (cherry picked from commit d189e58f63309a866ca039c0af396c52bdef86dd) * ansible-lint and molecule part of Red Hat (#47826) (cherry picked from commit 4572d9ccd776b88a2fc4f3f9ae5215962652f37d)
2018-10-30 19:45:41 +00:00
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:
Add the start of a coding guidelines document.
2014-01-26 21:42:21 +00:00
[stable-2.7] bulk docs update (#47828) * Document all Working Group, email lists and IRC channels (#47615) (cherry picked from commit 749af9fd2200e9895555734d9adac84c13275387) * Docs: No need to follow up on backport PRs (#47616) (cherry picked from commit 166e84b9c4fe63dd5ec4cec5f2dad5b24b9bc26e) * Tidy up Contributors Docs (#47619) (cherry picked from commit 72359a10e6cc0bef16b8742dd76355f0f1816dfe) * Correct AWX community link (#47742) (cherry picked from commit d189e58f63309a866ca039c0af396c52bdef86dd) * ansible-lint and molecule part of Red Hat (#47826) (cherry picked from commit 4572d9ccd776b88a2fc4f3f9ae5215962652f37d)
2018-10-30 19:45:41 +00:00
* [Contributing your module to Ansible](https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_checklist.html)
Add the start of a coding guidelines document.
2014-01-26 21:42:21 +00:00
[stable-2.7] bulk docs update (#47828) * Document all Working Group, email lists and IRC channels (#47615) (cherry picked from commit 749af9fd2200e9895555734d9adac84c13275387) * Docs: No need to follow up on backport PRs (#47616) (cherry picked from commit 166e84b9c4fe63dd5ec4cec5f2dad5b24b9bc26e) * Tidy up Contributors Docs (#47619) (cherry picked from commit 72359a10e6cc0bef16b8742dd76355f0f1816dfe) * Correct AWX community link (#47742) (cherry picked from commit d189e58f63309a866ca039c0af396c52bdef86dd) * ansible-lint and molecule part of Red Hat (#47826) (cherry picked from commit 4572d9ccd776b88a2fc4f3f9ae5215962652f37d)
2018-10-30 19:45:41 +00:00
* [Development conventions, tips and pitfalls](https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_best_practices.html)
Add the start of a coding guidelines document.
2014-01-26 21:42:21 +00:00
[stable-2.7] bulk docs update (#47828) * Document all Working Group, email lists and IRC channels (#47615) (cherry picked from commit 749af9fd2200e9895555734d9adac84c13275387) * Docs: No need to follow up on backport PRs (#47616) (cherry picked from commit 166e84b9c4fe63dd5ec4cec5f2dad5b24b9bc26e) * Tidy up Contributors Docs (#47619) (cherry picked from commit 72359a10e6cc0bef16b8742dd76355f0f1816dfe) * Correct AWX community link (#47742) (cherry picked from commit d189e58f63309a866ca039c0af396c52bdef86dd) * ansible-lint and molecule part of Red Hat (#47826) (cherry picked from commit 4572d9ccd776b88a2fc4f3f9ae5215962652f37d)
2018-10-30 19:45:41 +00:00
Our [Community Guide](https://docs.ansible.com/ansible/devel/community/) may also help you connect with the community of Ansible developers.
Reference in a new issue Copy permalink