ci: auto-roll project board status (epics In Progress on any progress) #360

Closed
opened 2026-07-02 05:12:40 +00:00 by manlycucumber · 0 comments
manlycucumber commented 2026-07-02 05:12:40 +00:00 (Migrated from github.com)

Problem

The org Project board never sets In Progress — closed items go to Done (built-in), but nothing moves an epic to In Progress when work begins, so every open epic sits in Todo regardless of progress.

Goal

A scheduled + event-driven GitHub Action that rolls the board Status for every issue in the project:

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

Acceptance criteria

  • Workflow added, project-wide (covers all repos via the shared project + hourly schedule)
  • No-ops safely until the PROJECTS_PAT secret is configured (org Projects v2 writes need a PAT, not GITHUB_TOKEN)
  • Idempotent (only writes when a status actually changes)

Notes

Maintainer step: add a PROJECTS_PAT secret (fine-grained PAT with Projects: read & write + repo issues read) so the Action can write the org project.

## Problem The org Project board never sets **In Progress** — closed items go to Done (built-in), but nothing moves an epic to In Progress when work begins, so every open epic sits in Todo regardless of progress. ## Goal A scheduled + event-driven GitHub Action that rolls the board Status for every issue in the project: - closed -> **Done** - open **epic** with any completed sub-issue -> **In Progress** (else Todo) - open **issue** with an open linked PR -> **In Progress** (else Todo) ## Acceptance criteria - [ ] Workflow added, project-wide (covers all repos via the shared project + hourly schedule) - [ ] No-ops safely until the `PROJECTS_PAT` secret is configured (org Projects v2 writes need a PAT, not GITHUB_TOKEN) - [ ] Idempotent (only writes when a status actually changes) ## Notes Maintainer step: add a `PROJECTS_PAT` secret (fine-grained PAT with **Projects: read & write** + repo issues read) so the Action can write the org project.
Sign in to join this conversation.
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#360
No description provided.