ward-kdl: list-all (auto-paginating) action for forgejo issue list #241
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/agentic-os#241
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Feature: a
list-all(auto-paginating) action for the forgejo surfaceward-kdl ops forgejo issue listalready exposes the raw Forgejo paging primitives--page(1-based) and--limit(page size) - the params coily's hand-rolledissue listnever had. So the missing piece is no longer a flag; it is the loop.The composite-verb DSL today (
cmd/ward-kdl/ward-kdl.forgejo.guardfile.kdl) has two step types:call <verb>- one granted call, threading$step.fielddata forward.poll <verb>- re-run the same call on an intervaluntila JMESPath condition holds, keeping the last result (used byci-watch).Neither accumulates across iterations. There is no step that walks
--pageand concatenates the page results into one collection. So a whole-backlog fetch still forces every caller to hand-loop pages outside ward-kdl.Ask
Add a
list-allaction on the forgejo surface that pages the grantedlist issueleaf and concatenates results until exhaustion - stop when a page returns fewer than--limititems, or gate onX-Total-Count. Inputs mirrorissue list(owner,repo,--state,--labels, ...) minus--page.Prefer generalizing the mechanism over a one-off: a reusable
paginate/collectstep type in the action DSL (loop alistleaf over an incrementing page param, accumulate into one array) would serve every paginatedlistleaf - issues, PRs, tasks, org members - not just this one.Consumer
agentic-os
goose-triage(scripts/goose-triage.py) fetches open issues viacoily ops forgejo issue list, which caps at 50 with no page flag, so on a backlog >50 it triages and now applies labels over a partial set and only warns. Once its fetch migrates ontoward-kdl ops forgejo issue list-all, that cap and the partial-backlog warning both go away. See agentic-osdocs/goose-triage.md.Moved from coilyco-flight-deck/agentic-os#241 (originally scoped as a goose-triage-local page loop; the real fix is this ward-kdl primitive).
goose-triage: paginated fetch for whole-backlog triageto ward-kdl: list-all (auto-paginating) action for forgejo issue listcoilyco-flight-deck/ward#131