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

Add filtering and fleet-wide rollup/summary mode #1

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

SPEC.md roadmap item 1.

For ~80 projects the full tree is a lot to read serially. Add:

  • --filter <project-glob> to scope a scan to matching project names.
  • A summary/rollup mode that answers fleet-wide questions without walking
    the whole tree, e.g.:
    • N projects have no pipeline file
    • N pipelines share step image X (grouped by image)
    • N steps have no when (see #3 — related but separate: this issue is
      about counting, #3 is about flagging in the tree)

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

Acceptance criteria

  • -filter <glob> flag restricts scan output to projects whose name matches (tree and -json both respect it)
  • a -summary (or equivalent) mode prints counts: projects with no pipeline file, pipelines grouped by shared step image, steps with no when
  • both flags documented in README usage section
  • verified against ~/projects with at least one non-trivial glob and cross-checked by hand against a couple of matches
SPEC.md roadmap item 1. For ~80 projects the full tree is a lot to read serially. Add: - `--filter <project-glob>` to scope a scan to matching project names. - A summary/rollup mode that answers fleet-wide questions without walking the whole tree, e.g.: - N projects have no pipeline file - N pipelines share step image X (grouped by image) - N steps have no `when` (see #3 — related but separate: this issue is about *counting*, #3 is about *flagging in the tree*) Source: [SPEC.md](https://git.oleks.space/oleks/pipetree/src/branch/main/SPEC.md#roadmap), review feedback captured on commit `4b5b336`. ## Acceptance criteria - [ ] `-filter <glob>` flag restricts scan output to projects whose name matches (tree and `-json` both respect it) - [ ] a `-summary` (or equivalent) mode prints counts: projects with no pipeline file, pipelines grouped by shared step image, steps with no `when` - [ ] both flags documented in README usage section - [ ] verified against `~/projects` with at least one non-trivial glob and cross-checked by hand against a couple of matches
oleks added this to the v0.2 — Fleet audit basics milestone 2026-08-01 15:41:47 +03:00
oleks added the enhancement label 2026-08-01 15:41:47 +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).

Resolved by f10a008 (v0.2 batch push).
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.
Blocks
#5 Cross-pipeline structural analysis: shared images, unreachable steps, orphaned files
oleks/pipetree
#7 Wrap pipetree as an MCP server (scan / filter / pipeline_health tools)
oleks/pipetree
Reference: oleks/pipetree#1
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?