Convert Blocked by sections into native Forgejo dependencies #494

Closed
opened 2026-10-21 10:06:38 +00:00 by root · 6 comments
root commented 2026-10-21 10:06:38 +00:00 (Migrated from gitlab.core-project.space)

Parent

#489

What to build

On switch day, open specs keep their order: a script reads every imported issue's ## Blocked by section and creates the matching native Forgejo issue dependencies, then removes the section. It reports what it did and what it skipped. It runs once, on switch day, from the checklist.

Seam: a node --test suite for the converter on fixture issue bodies (spec ## Seams).

Acceptance criteria

  • An issue with no ## Blocked by section is left alone.
  • "None (can start immediately)" creates no dependency and removes the section.
  • Several blockers create one dependency each.
  • A blocker not in the project is reported and skipped, never fatal.
  • A dry run prints the plan without writing.
  • A second run creates nothing new.
## Parent #489 ## What to build On switch day, open specs keep their order: a script reads every imported issue's `## Blocked by` section and creates the matching native Forgejo issue dependencies, then removes the section. It reports what it did and what it skipped. It runs once, on switch day, from the checklist. Seam: a `node --test` suite for the converter on fixture issue bodies (spec `## Seams`). ## Acceptance criteria - [ ] An issue with no `## Blocked by` section is left alone. - [ ] "None (can start immediately)" creates no dependency and removes the section. - [ ] Several blockers create one dependency each. - [ ] A blocker not in the project is reported and skipped, never fatal. - [ ] A dry run prints the plan without writing. - [ ] A second run creates nothing new.
root commented 2026-10-21 10:07:19 +00:00 (Migrated from gitlab.core-project.space)

mentioned in issue #498

mentioned in issue #498
root commented 2026-10-21 10:08:13 +00:00 (Migrated from gitlab.core-project.space)

marked this issue as related to #489

marked this issue as related to #489
root commented 2026-10-21 10:08:36 +00:00 (Migrated from gitlab.core-project.space)

marked this issue as related to #498

marked this issue as related to #498
root commented 2026-10-21 10:23:41 +00:00 (Migrated from gitlab.core-project.space)

mentioned in commit 6ec8961241

mentioned in commit 6ec89612410a574965a3ec1a06143e3475b4ceab
root commented 2026-10-21 10:23:55 +00:00 (Migrated from gitlab.core-project.space)

mentioned in merge request !568

mentioned in merge request !568
root commented 2026-10-22 09:46:36 +00:00 (Migrated from gitlab.core-project.space)

mentioned in commit 60d076f248

mentioned in commit 60d076f24843d3282d9f08d4b1d2fde6d6f236ac
root (Migrated from gitlab.core-project.space) closed this issue 2026-10-22 09:54:51 +00:00
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.

Reference
amaurycoudr/chess-project#494
No description provided.