oleks/pipetree
1
0
Fork 0
Code Issues 3 Pull Requests Actions Packages Projects Releases Wiki Activity

Suppress vendored/fixture-repo noise in fleet-wide scans #2

New Issue
Closed
opened 2026-08-01 15:41:55 +03:00 by oleks · 1 comment
oleks commented 2026-08-01 15:41:55 +03:00
Owner
Copy Link
Copy Source

SPEC.md roadmap item 2.

Scanning ~/projects picks up the upstream woodpecker repo's own
test-fixture corpus (test-dag, test-merge-map-and-sequence, test-when,
~24 fixture "pipelines") — correct behavior (good evidence the YAML edge
cases are handled) but noise: that's woodpecker's linter test corpus, not
real CI surface, and it clutters fleet-wide runs.

Candidate approaches (pick one, or layer):

  • Heuristic: skip a project whose .git remote doesn't point at
    git.oleks.space/oleks/*.
  • Explicit .pipetreeignore file / --exclude <glob> flag.

Source: SPEC.md, review feedback captured on commit 4b5b336.

Acceptance criteria

  • decide and implement one exclusion mechanism (remote-based heuristic and/or .pipetreeignore/-exclude)
  • a fleet-wide scan of ~/projects no longer lists the woodpecker mirror's own fixture pipelines by default
  • the exclusion is overridable (a flag to include everything, for when someone genuinely wants the full picture)
  • documented in README
SPEC.md roadmap item 2. Scanning `~/projects` picks up the upstream `woodpecker` repo's own test-fixture corpus (`test-dag`, `test-merge-map-and-sequence`, `test-when`, ~24 fixture "pipelines") — correct behavior (good evidence the YAML edge cases are handled) but noise: that's woodpecker's linter test corpus, not real CI surface, and it clutters fleet-wide runs. Candidate approaches (pick one, or layer): - Heuristic: skip a project whose `.git` remote doesn't point at `git.oleks.space/oleks/*`. - Explicit `.pipetreeignore` file / `--exclude <glob>` flag. Source: [SPEC.md](https://git.oleks.space/oleks/pipetree/src/branch/main/SPEC.md#roadmap), review feedback captured on commit `4b5b336`. ## Acceptance criteria - [ ] decide and implement one exclusion mechanism (remote-based heuristic and/or `.pipetreeignore`/`-exclude`) - [ ] a fleet-wide scan of `~/projects` no longer lists the `woodpecker` mirror's own fixture pipelines by default - [ ] the exclusion is overridable (a flag to include everything, for when someone genuinely wants the full picture) - [ ] documented in README
oleks added this to the v0.2 — Fleet audit basics milestone 2026-08-01 15:41:55 +03:00
oleks added the enhancement label 2026-08-01 15:41:55 +03:00
oleks closed this issue 2026-08-01 16:21:25 +03:00
oleks commented 2026-08-01 17:21:24 +03:00
Author
Owner
Copy Link
Copy Source

Resolved by f10a008 (v0.2 batch push). Verified: the woodpecker mirror's real remote is github.com/retif/woodpecker, so it's excluded by default; -all restores it.

Resolved by f10a008 (v0.2 batch push). Verified: the woodpecker mirror's real remote is github.com/retif/woodpecker, so it's excluded by default; -all restores it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
New capability or improvement
No labels enhancement
Milestone
No items
No Milestone v0.2 — Fleet audit basics
Projects
Clear projects
No projects
Assignees
Clear assignees
oleks
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: oleks/pipetree#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?