ci: auto-roll project board status by progress (#360) #361

Merged
manlycucumber merged 1 commit from feature/360-project-status-rollup into develop 2026-07-02 05:15:25 +00:00
manlycucumber commented 2026-07-02 05:14:19 +00:00 (Migrated from github.com)

Closes #360.

Adds a scheduled + event-driven workflow that keeps the org Project board's Status in sync with real progress, so epics stop sitting in Todo forever:

  • closed issue → Done
  • open epic with a completed sub-issue → In Progress (else Todo)
  • open issue with an open linked PR → In Progress (else Todo)

One copy in Core rolls up the whole project (all repos) via the hourly schedule; Core issue/PR events give faster updates for the active repo. Idempotent — only writes when a status actually changes.

Maintainer step to activate: add a PROJECTS_PAT repo/org secret — a fine-grained PAT with Projects: read & write (and repo Issues/PRs: read). Until then the workflow no-ops cleanly (guard step emits a notice and skips). Org Projects v2 writes can't use GITHUB_TOKEN, hence the PAT.

Validated: YAML structure + embedded github-script JS syntax check locally.

Closes #360. Adds a scheduled + event-driven workflow that keeps the org Project board's **Status** in sync with real progress, so epics stop sitting in Todo forever: - closed issue → **Done** - open **epic** with a completed sub-issue → **In Progress** (else Todo) - open **issue** with an open linked PR → **In Progress** (else Todo) One copy in Core rolls up the **whole project** (all repos) via the hourly schedule; Core issue/PR events give faster updates for the active repo. Idempotent — only writes when a status actually changes. **Maintainer step to activate:** add a `PROJECTS_PAT` repo/org secret — a fine-grained PAT with **Projects: read & write** (and repo Issues/PRs: read). Until then the workflow **no-ops cleanly** (guard step emits a notice and skips). Org Projects v2 writes can't use `GITHUB_TOKEN`, hence the PAT. Validated: YAML structure + embedded github-script JS syntax check locally.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Directorium/Core!361
No description provided.