fix(ci): milestone-sync creates and syncs Forgejo issues per checklist item #13

Merged
neerdoc merged 2 commits from fix/ci-milestone-sync--issue-creation into main 2026-05-31 18:22:47 +00:00
Owner
  • spec(ci): bump ci-milestone-sync.spec.md to v0.3.0; add REQ-CI-008/009/010 and ACC-CI-007/008/009 specifying that one Forgejo issue is created per phase gate checklist item, assigned to the phase milestone, and kept open/closed in sync with the [x]/[ ] state
  • fix(ci): rewrite milestone-sync.sh to create/sync issues — for each checklist item the script now creates a [Phase N] <item text> issue assigned to the milestone (idempotent by title match), and closes or reopens it to match the roadmap checklist state; milestone description and state behaviour is unchanged

Note: /code-review not run on this branch — this is bash + spec only, no Rust. Flagging for awareness per review policy.

- spec(ci): bump ci-milestone-sync.spec.md to v0.3.0; add REQ-CI-008/009/010 and ACC-CI-007/008/009 specifying that one Forgejo issue is created per phase gate checklist item, assigned to the phase milestone, and kept open/closed in sync with the [x]/[ ] state - fix(ci): rewrite milestone-sync.sh to create/sync issues — for each checklist item the script now creates a `[Phase N] <item text>` issue assigned to the milestone (idempotent by title match), and closes or reopens it to match the roadmap checklist state; milestone description and state behaviour is unchanged Note: /code-review not run on this branch — this is bash + spec only, no Rust. Flagging for awareness per review policy.
REQ-CI-008, REQ-CI-009, REQ-CI-010 specify that the sync script must
create a Forgejo issue for each phase gate checklist item, assign it to
the phase milestone, and keep its open/closed state in sync with the
[x]/[ ] mark. ACC-CI-007 through ACC-CI-009 cover idempotency.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
fix(ci): milestone-sync creates and syncs Forgejo issues per checklist item
All checks were successful
Gate Check-off / checkoff (pull_request) Successful in 4s
Milestone Sync / sync (pull_request) Successful in 1m4s
e53c657d8a
Previously the script only created milestones with a description text
but never populated them with issues, so the Forgejo progress bar was
always empty.

Now, for each Phase Gate Checklist item the script creates a
[Phase N] <item text> issue assigned to the milestone (idempotent), and
closes or reopens the issue to match the [x]/[ ] state in the roadmap
file.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
neerdoc left a comment

Looks ok.

Looks ok.

Milestone Progress

Phase gate checklist status:

  • Phase 0 — Prior Art Analysis: 6/6 items
  • Phase 1 — Core Domain Model: 0/12 items
  • Phase 2 — REST API + AuthN/AuthZ: 0/10 items
  • Phase 3 — BOM Management: 0/9 items
  • Phase 4 — ECO/ECR Workflow Engine: 0/9 items
  • Phase 5 — UI (htmx): 0/8 items
### Milestone Progress Phase gate checklist status: - [x] **Phase 0 — Prior Art Analysis**: 6/6 items - [ ] **Phase 1 — Core Domain Model**: 0/12 items - [ ] **Phase 2 — REST API + AuthN/AuthZ**: 0/10 items - [ ] **Phase 3 — BOM Management**: 0/9 items - [ ] **Phase 4 — ECO/ECR Workflow Engine**: 0/9 items - [ ] **Phase 5 — UI (htmx)**: 0/8 items
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
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
WulfScience-FOSS/patina!13
No description provided.