fix(ci): run lint when its own config changes #42

Merged

jfraeys merged 1 commit from jfraeys/fix/lint-trigger-config-files into main 2026-10-10 10:47:05 -04:00

Conversation 0 Commits 1 Files changed 1 +2

jfraeys commented 2026-10-10 10:42:00 -04:00

Owner

Copy link

Why the "Directory expansion discovered 166 file(s)" warning was still visible after #40: the log was run 262, PR #41, whose branch predates #40 (its .ansible-lint has no new exclusions). And #40 itself changed only .ansible-lint, which none of lint.yml paths matched, so lint never ran for it.

Adds .ansible-lint and .yamllint to the pull_request path filter. This PR touches lint.yml, so its own lint run (branch cut from current main) should show the new file count (locally: 167 -> 93 files processed).

🤖 Generated with Claude Code

Why the "Directory expansion discovered 166 file(s)" warning was still visible after #40: the log was run 262, PR #41, whose branch predates #40 (its .ansible-lint has no new exclusions). And #40 itself changed only .ansible-lint, which none of lint.yml paths matched, so lint never ran for it. Adds .ansible-lint and .yamllint to the pull_request path filter. This PR touches lint.yml, so its own lint run (branch cut from current main) should show the new file count (locally: 167 -> 93 files processed). 🤖 Generated with [Claude Code](https://claude.com/claude-code)

jfraeys added 1 commit 2026-10-10 10:42:00 -04:00

fix(ci): run lint when its own config changes ... 24a2dca340

lint.yml only triggered on roles/, playbooks/, scripts/, terraform/ and itself,
so a change to .ansible-lint or .yamllint (e.g. the exclude_paths narrowing in
#40) never ran lint in CI and could not be verified there.

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

jfraeys merged commit 4f547e1127 into main 2026-10-10 10:47:05 -04:00

jfraeys referenced this pull request from a commit 2026-10-10 10:47:07 -04:00

Merge pull request 'fix(ci): run lint when its own config changes' (#42) from jfraeys/fix/lint-trigger-config-files into main

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No labels

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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!42

No description provided.