UI for linking specs to Forgejo issues (manual link + create-issue button) #24

Closed
opened 2026-10-31 19:01:09 +00:00 by Gilles · 0 comments
Owner

Frontend for the first slice of the Forgejo issue <-> spec link feature (see backend thierryade/backend#25, same scope split).

Scope (PR 1 of 3):

  • On SpecDetailView: a "liens issues" section listing linked issues (repo + number + cached title + state badge), with a form to add a manual link (repo + issue number) and a delete action per link.
  • Button "Creer l'issue Forgejo": pre-fills target repo from the project's default_repo (editable override), calls the create-issue API action, shows the resulting link once created.
  • implemented checkbox becomes read-only/greyed with a tooltip ("derive des issues liees") as soon as the spec has >=1 link.
  • Project admin/settings: field to set default_repo.

No live state sync yet (polling/webhook is thierryade/backend#25's PR 2 follow-up) -- cached_state is whatever the backend returned at link creation time until then.

Frontend for the first slice of the Forgejo issue <-> spec link feature (see backend thierryade/backend#25, same scope split). Scope (PR 1 of 3): - On `SpecDetailView`: a "liens issues" section listing linked issues (repo + number + cached title + state badge), with a form to add a manual link (repo + issue number) and a delete action per link. - Button "Creer l'issue Forgejo": pre-fills target repo from the project's `default_repo` (editable override), calls the create-issue API action, shows the resulting link once created. - `implemented` checkbox becomes read-only/greyed with a tooltip ("derive des issues liees") as soon as the spec has >=1 link. - `Project` admin/settings: field to set `default_repo`. No live state sync yet (polling/webhook is thierryade/backend#25's PR 2 follow-up) -- `cached_state` is whatever the backend returned at link creation time until then.
Sign in to join this conversation.
No description provided.