From 77b32b8e7829c1efad27937cb72439dbad089b81 Mon Sep 17 00:00:00 2001 From: Andrew Klychkov Date: Sat, 27 Mar 2021 07:23:44 +0100 Subject: [PATCH] Add suggested --- REVIEW_CHECKLIST.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/REVIEW_CHECKLIST.md b/REVIEW_CHECKLIST.md index 7ab7e87..f3a6994 100644 --- a/REVIEW_CHECKLIST.md +++ b/REVIEW_CHECKLIST.md @@ -18,7 +18,7 @@ When reviewing, keep in mind that we follow [Ansible Code of Conduct](https://do - [ ] the changes follow the [Ansible documentation standards](https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_documenting.html) and the [style guide](https://docs.ansible.com/ansible/devel/dev_guide/style_guide/index.html#style-guide) - [ ] the changes follow the [development conventions](https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_best_practices.html) - [ ] if a new plugin is added, it is one of the [allowed plugin types](https://github.com/ansible-collections/overview/blob/main/collection_requirements.rst#modules-plugins) -- [ ] documentation, examples, and return sections use FQCNs for `M(..)` when referring to modules +- [ ] documentation, examples, and return sections use FQCNs for the `M(..)` [format macros](https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_documenting.html#linking-and-other-format-macros-within-module-documentation) when referring to modules - [ ] modules and plugins from ansible-core use `ansible.builtin.` as a FQCN prefix when mentioned - [ ] when a new option, module, plugin, or return value is added, the corresponding documentation or return sections use `version_added:` containing the *collection* version for which they were added - [ ] FQCNs are used for `extends_documentation_fragment:`, unless the author is referring to doc_fragments from ansible-core