fix: scope smoke-init CI to init-related changes only #8

New issue

Closed

opened 2026-03-28 10:26:12 +00:00 by dev-bot · 0 comments

dev-bot commented

2026-03-28 10:26:12 +00:00

Collaborator

Problem

The smoke-init workflow runs on every push and PR, even when the changes don't touch disinto init or related code. It spins up a full Forgejo instance inside CI, which is slow and wastes resources on unrelated PRs.

Fix

Add a path filter to .woodpecker/smoke-init.yml so it only triggers when init-related files change:

when:
  event: [push, pull_request]
  path:
    - "bin/disinto"
    - "lib/env.sh"
    - "lib/load-project.sh"
    - "tests/smoke-init.sh"
    - ".woodpecker/smoke-init.yml"
    - "docker/agents/**"

This keeps the full end-to-end init test but avoids running it on PRs that only touch agents, formulas, or other unrelated code.

## Problem The `smoke-init` workflow runs on every push and PR, even when the changes don't touch `disinto init` or related code. It spins up a full Forgejo instance inside CI, which is slow and wastes resources on unrelated PRs. ## Fix Add a `path` filter to `.woodpecker/smoke-init.yml` so it only triggers when init-related files change: ```yaml when: event: [push, pull_request] path: - "bin/disinto" - "lib/env.sh" - "lib/load-project.sh" - "tests/smoke-init.sh" - ".woodpecker/smoke-init.yml" - "docker/agents/**" ``` This keeps the full end-to-end init test but avoids running it on PRs that only touch agents, formulas, or other unrelated code.