chore(lint): make .yamllint comply with ansible-lint's requirements #25

Closed
jfraeys wants to merge 0 commits from jfraeys/chore/yamllint-ansible-lint-compat into main AGit
Owner

ansible-lint warned on every CI run that the custom .yamllint is incompatible (comments.min-spaces-from-content must be 1, braces.max-spaces-inside 1, octal-values forbid implicit and explicit octals). Those three are set; yamllint still reports no findings across roles, playbooks, inventory and .forgejo, and ansible-lint passes with the same toolchain as CI (Python 3.11, requirements.txt). The separate "Directory expansion discovered 166 file(s)" warning is not addressed here. -- Generated with Claude Code

ansible-lint warned on every CI run that the custom .yamllint is incompatible (comments.min-spaces-from-content must be 1, braces.max-spaces-inside 1, octal-values forbid implicit and explicit octals). Those three are set; yamllint still reports no findings across roles, playbooks, inventory and .forgejo, and ansible-lint passes with the same toolchain as CI (Python 3.11, requirements.txt). The separate "Directory expansion discovered 166 file(s)" warning is not addressed here. -- Generated with [Claude Code](https://claude.com/claude-code)
ansible-lint warned on every CI run that the custom .yamllint is incompatible:
comments.min-spaces-from-content must be 1, braces.max-spaces-inside 1 and
octal-values forbid implicit/explicit octals. Set those; yamllint still
reports no findings across roles, playbooks, inventory and .forgejo.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Author
Owner

Closing: this PR's head commit is already an ancestor of main (merged through another path), so there is nothing left to merge. Verified with git merge-base --is-ancestor.

Closing: this PR's head commit is already an ancestor of main (merged through another path), so there is nothing left to merge. Verified with git merge-base --is-ancestor.
jfraeys closed this pull request 2026-10-13 09:47:58 -04:00

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
jfraeys/infra!25
No description provided.