Summary
The current ansible agent rules need to be reviewed for two issues:
1. Dependabot does not support Ansible
The cicd agent rules instruct agents to create a .github/dependabot.yml with package-ecosystem: 'npm' and github-actions entries. However, when those rules are applied to an ansible project, agents may incorrectly add a dependabot config — Dependabot has no supported package ecosystem for Ansible (ansible-galaxy, requirements.yml, collections). Adding a dependabot entry for an unsupported ecosystem either does nothing or causes confusing noise.
Action needed:
- The
ansible/ansible-linting.md and ansible/ansible-cicd.md rules (if they exist, or the shared cicd rules when applied to ansible) should explicitly state that Dependabot does not support Ansible and should not be configured for it.
- The shared
common/cicd.md rules should either note the ansible exception or the ansible-specific rules should override/suppress the dependabot section.
2. Verify pre-commit linting and git-hooks setup for Ansible
The ansible/ansible-git-hooks.md rules specify pre-commit as the hook tool, and ansible/ansible-linting.md documents ansible-lint and yamllint as the baseline tools. This is the correct approach for Ansible. However, the rules should be audited to confirm:
References
ansible/ansible-linting.md — baseline tooling: ansible-lint, yamllint
ansible/ansible-git-hooks.md — hook strategy: pre-commit
common/cicd.md — Dependabot configuration (npm + github-actions; does not mention ansible exception)
Summary
The current ansible agent rules need to be reviewed for two issues:
1. Dependabot does not support Ansible
The
cicdagent rules instruct agents to create a.github/dependabot.ymlwithpackage-ecosystem: 'npm'andgithub-actionsentries. However, when those rules are applied to an ansible project, agents may incorrectly add a dependabot config — Dependabot has no supported package ecosystem for Ansible (ansible-galaxy,requirements.yml, collections). Adding a dependabot entry for an unsupported ecosystem either does nothing or causes confusing noise.Action needed:
ansible/ansible-linting.mdandansible/ansible-cicd.mdrules (if they exist, or the sharedcicdrules when applied to ansible) should explicitly state that Dependabot does not support Ansible and should not be configured for it.common/cicd.mdrules should either note the ansible exception or the ansible-specific rules should override/suppress the dependabot section.2. Verify pre-commit linting and git-hooks setup for Ansible
The
ansible/ansible-git-hooks.mdrules specifypre-commitas the hook tool, andansible/ansible-linting.mddocumentsansible-lintandyamllintas the baseline tools. This is the correct approach for Ansible. However, the rules should be audited to confirm:ansible-linting.mdexplicitly recommendspre-commitfor local hook enforcement (coordinate withgit-hooksrules)ansible-git-hooks.mdconfigures.pre-commit-config.yamlwith the correct hooks:ansible-lint,yamllint, andansible-playbook --syntax-checkpre-commit autoupdateworkflow is documentedReferences
ansible/ansible-linting.md— baseline tooling:ansible-lint,yamllintansible/ansible-git-hooks.md— hook strategy:pre-commitcommon/cicd.md— Dependabot configuration (npm + github-actions; does not mention ansible exception)