4373863f25
* required_if checks should have three or four parts. * Validate mutually_exclusive, required_together, required_one_of, required_if and required_by. * Simplify code. * Improve messages. * Add changelog. * Sanity check. * Update docs. * Update ignore.txt. * Don't continue with tests when terms are not strings. * Remove ignore.txt entry. * Make sure validate-modules doesn't choke on things already flagged by schema test. * Check required_if requirements list for strings. |
||
|---|---|---|
| .. | ||
| _extensions | ||
| _static | ||
| _themes/sphinx_rtd_theme | ||
| js/ansible | ||
| rst | ||
| .gitignore | ||
| .nojekyll | ||
| jinja2.inv | ||
| keyword_desc.yml | ||
| Makefile | ||
| Makefile.sphinx | ||
| modules.js | ||
| python2.inv | ||
| python3.inv | ||
| README.md | ||
| requirements.txt | ||
| variables.dot | ||
Ansible documentation
This project hosts the source behind docs.ansible.com.
To create clear, concise, and consistent contributions to Ansible documentation, please refer to the following information.
Contributions
Contributions to the documentation are welcome.
The Ansible community produces guidance on contributions, building documentation, and submitting pull requests, which you can find in Contributing to the Ansible Documentation.
You can also join the Docs Working Group.
Ansible style guide
Ansible documentation is written in ReStructuredText(RST). The Ansible style guide provides linguistic direction and technical guidelines for working with reStructuredText, in addition to other resources.
Tools
The Ansible community uses a range of tools and programs for working with Ansible documentation. Learn more about Other Tools and Programs in the Ansible Community Guide.
GitHub
Ansible documentation is hosted on the Ansible GitHub project. For GitHub workflows and other information, see the GitHub Guides.