feature: UI for linking specs to Forgejo issues #25

Merged

Gilles merged 1 commit from feat/spec-issue-links into main

2026-10-31 19:40:09 +00:00

Gilles commented

2026-10-31 19:19:27 +00:00

Owner

Closes #24.

Frontend for thierryade/backend#26: on SpecDetailPanel, an "Issues Forgejo" section lists linked issues (repo#number, cached state/title, sync error if any), lets a writer link an existing issue manually or create one directly from the spec (defaulting to the project's default_repo, overridable). The "Implémentée" row now shows a read-only, derived state once the spec has >=1 link instead of the manual toggle (implementation_source: "manual" | "issues" | null).

AdminProjectsTab gets a "Dépôt Forgejo" editor next to the existing code-prefix one, for setting Project.default_repo.

No live sync after creation yet (webhook/polling is a later slice) -- cached_state/title come from whatever the backend returned at creation time.

Test plan

pnpm run test:unit -- 85/85 passing (5 new)
vue-tsc -b -- clean
vite build -- clean

🤖 Generated with Claude Code

https://claude.ai/code/session_014HiJrn6J6vhyFfC2qyY4uh

Closes #24. Frontend for `thierryade/backend#26`: on `SpecDetailPanel`, an "Issues Forgejo" section lists linked issues (repo#number, cached state/title, sync error if any), lets a writer link an existing issue manually or create one directly from the spec (defaulting to the project's `default_repo`, overridable). The "Implémentée" row now shows a read-only, derived state once the spec has >=1 link instead of the manual toggle (`implementation_source`: "manual" | "issues" | null). `AdminProjectsTab` gets a "Dépôt Forgejo" editor next to the existing code-prefix one, for setting `Project.default_repo`. No live sync after creation yet (webhook/polling is a later slice) -- `cached_state`/title come from whatever the backend returned at creation time. ## Test plan - [x] `pnpm run test:unit` -- 85/85 passing (5 new) - [x] `vue-tsc -b` -- clean - [x] `vite build` -- clean --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_014HiJrn6J6vhyFfC2qyY4uh

Gilles added 1 commit

2026-10-31 19:19:27 +00:00

feature: UI for linking specs to Forgejo issues

ci / unit (pull_request) Successful in 1m11s

Details

ci / publish (pull_request) Has been skipped

Details

c6e36cc08d

Closes #24.

Frontend for thierryade/backend#25/#26: on SpecDetailPanel, an "Issues
Forgejo" section lists linked issues (repo#number, cached state/title,
sync error if any), lets a writer link an existing issue manually or
create one directly from the spec (defaulting to the project's
default_repo, overridable). The "Implémentée" row now shows a
read-only, derived state once the spec has >=1 link instead of the
manual toggle (implementation_source: "manual" | "issues" | null).

AdminProjectsTab gets a "Dépôt Forgejo" editor next to the existing
code-prefix one, for setting Project.default_repo.

No live sync after creation yet (webhook/polling is a later slice) --
cached_state/title come from whatever the backend returned at creation
time.

## Test plan
- [x] `pnpm run test:unit` -- 85/85 passing (5 new)
- [x] `vue-tsc -b` -- clean
- [x] `vite build` -- clean

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014HiJrn6J6vhyFfC2qyY4uh

Gilles added the

feature

label

2026-10-31 19:19:31 +00:00

Gilles commented

2026-10-31 19:20:37 +00:00

Author

Owner