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

Flag steps/pipelines with no when (implicit always-run) in the tree #3

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

SPEC.md roadmap item 2b.

Woodpecker treats a step or pipeline with no when clause as "always
run" — easy to write by accident, and currently invisible in pipetree's
output (absence of a when: line reads the same whether it's intentional
or a forgotten condition). Make it explicit: annotate when-less
steps/pipelines in the tree (e.g. [always-run]) instead of just omitting
the line.

Complements #1 (rollup mode should be able to count these fleet-wide).

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

Acceptance criteria

  • a pipeline or step with no when at all renders an explicit [always-run] marker in tree output
  • the same is represented in -json output (e.g. an always_run: true field, not just an empty when array — those two cases must be distinguishable)
  • rollup mode from #1 can count these fleet-wide
  • verified against at least one real always-run pipeline in ~/projects
SPEC.md roadmap item 2b. Woodpecker treats a step or pipeline with no `when` clause as "always run" — easy to write by accident, and currently invisible in pipetree's output (absence of a `when:` line reads the same whether it's intentional or a forgotten condition). Make it explicit: annotate `when`-less steps/pipelines in the tree (e.g. `[always-run]`) instead of just omitting the line. Complements #1 (rollup mode should be able to count these fleet-wide). Source: [SPEC.md](https://git.oleks.space/oleks/pipetree/src/branch/main/SPEC.md#roadmap), review feedback captured on commit `4b5b336`. ## Acceptance criteria - [ ] a pipeline or step with no `when` at all renders an explicit `[always-run]` marker in tree output - [ ] the same is represented in `-json` output (e.g. an `always_run: true` field, not just an empty `when` array — those two cases must be distinguishable) - [ ] rollup mode from #1 can count these fleet-wide - [ ] verified against at least one real always-run pipeline in `~/projects`
oleks added this to the v0.2 — Fleet audit basics milestone 2026-08-01 15:42:02 +03:00
oleks added the enhancement label 2026-08-01 15:42:02 +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.
Dependencies

No dependencies set.

Reference: oleks/pipetree#3
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?