# \[Vote ended on 2024-01-30\] Ansible collection inclusion requirements: remove absolute ban of \`undocumented-parameter\` ignore.txt entry

**URL:** <https://forum.ansible.com/t/vote-ended-on-2024-01-30-ansible-collection-inclusion-requirements-remove-absolute-ban-of-undocumented-parameter-ignore-txt-entry/3055>\
**Category:** Project Discussions\
**Tags:** implemented, requirements, collections, community-wg\
**Created:** [December 23, 2023, 12:28pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-30-ansible-collection-inclusion-requirements-remove-absolute-ban-of-undocumented-parameter-ignore-txt-entry/3055 "2023-12-23T12:28:05Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jborean](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/jborean/32/1525_2.png) [@jborean](https://forum.ansible.com/u/jborean)\
**Post date:** [January 3, 2024, 7:28pm UTC](https://forum.ansible.com/t/vote-ended-on-2024-01-30-ansible-collection-inclusion-requirements-remove-absolute-ban-of-undocumented-parameter-ignore-txt-entry/3055/3 "2024-01-03T19:28:48Z")

</div>

Why not just document it and say it’s for internal use only. While I would love for a way to explicitly mark something as internal only so you don’t have to document it at all, I find that using the ignore files is the wrong thing for something like this.

---

_[View the full topic](https://forum.ansible.com/t/vote-ended-on-2024-01-30-ansible-collection-inclusion-requirements-remove-absolute-ban-of-undocumented-parameter-ignore-txt-entry/3055)._