ci: flip an epic to In Progress on any started sub-issue #362
No reviewers
Labels
No labels
area: build
area: ci
area: compare
area: data
area: engine
area: model
area: provenance
area: rite
area: validation
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
github_actions
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: bug
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Core!362
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/rollup-any-progress"
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?
What
The board rollup only promoted an epic to In Progress once one of its sub-issues was completed (closed). An epic with active-but-unmerged work therefore sat in Todo — the opposite of the goal ("show In Progress as soon as we begin work on one").
Verifying the newly-added
PROJECTS_PATsurfaced this: the first authenticated rollup reverted Epic #38 from In Progress back to Todo, because #38's children are underway but none are closed yet.Change
Treat an epic as In Progress when any sub-issue has started — i.e. is closed OR has an open linked PR — by reading each epic's
subIssuesin the GraphQL query and checking them. Individual-issue and closed→Done behaviour is unchanged.Refs #360.