Bradley A. Thornton

The goal here is to look inside the ansible-test ignore file and ensure certain things are not being skipped e.g. this file: https://github.com/ansible-collections/cisco.nxos/blob/main/tests/sanity/ignore-2.10.txt

Related: https://github.com/ansible/galaxy-importer/blob/b7140d6b3b5e172553788ae9aaa7526f8ff49ea2/galaxy_importer/loaders/collection.py#L99

incl compound words: https://github.com/ansible/ansible-navigator/issues/1221

I believe the issue is in `write_comment`, I was able to work around it with: ``` if ( pre and not value.strip() and not isinstance( self.event, ( ruamel.yaml.events.CollectionEndEvent, ruamel.yaml.events.DocumentEndEvent, ruamel.yaml.events.StreamEndEvent,...

@ssbarnea Yes! One blank line between each task would be a really nice default. I think it makes for very readable task files.....

I like the idea of this as an opt-in rule. We might need to wait for profile support to enforce it somewhere.

I believe we should be able to load the `when` clause with jinja2 and introspect the resulting object to determine if it is complex, quick example, this way we could...

this might/should also include a check that the required_ansible version is indeed a still supported version of ansible

seems sane to me, does this leave the door open for subrule disable support? ``` rules: name: exclude_paths: - "*.*" subrules: - block: false - import_play: true #default - tasks:...

RE reformatting, we can use jinja's internals to ensure the meaning isn't changed