size[block]: Limit the maximum block depth #2173
Labels
good first issue
Bugs ideal for the first time, good for newcomers contributors
new rule
A request for a new rule
Starting to pull in possible rule ideas from the community of practice: redhat-cop/automation-good-practices#64
Ofter, using an include within a block leads to more readable playbooks and task file vs. a deep block depth.
It might not be possible to check across files and I'm not sure lint tracks block state, but within a single file we should be able to limit it.
2 was suggested only as a starting point
The text was updated successfully, but these errors were encountered: