Backend Issue 10: Add Board Repository Linking APIs #11

New Issue

Closed

opened 2026-05-19 02:28:00 -05:00 by null · 0 comments

null commented

2026-05-19 02:28:00 -05:00

Owner

Goal

Let Pipeline boards declare which tracked Forgejo repositories belong to that board.

Suggested Endpoints

GET /api/v1/boards/{board_id}/forgejo/repositories
POST /api/v1/boards/{board_id}/forgejo/repositories
DELETE /api/v1/boards/{board_id}/forgejo/repositories/{repository_id}

Acceptance Criteria

Board writers can attach/detach tracked repositories.
Board readers can list linked repositories.
Duplicate links are rejected or treated idempotently.
Tests cover access checks, duplicate behavior, and cross-organization rejection.

Out Of Scope

Agent issue routes, Issue closing, Frontend UI.

## Goal Let Pipeline boards declare which tracked Forgejo repositories belong to that board. ## Suggested Endpoints - `GET /api/v1/boards/{board_id}/forgejo/repositories` - `POST /api/v1/boards/{board_id}/forgejo/repositories` - `DELETE /api/v1/boards/{board_id}/forgejo/repositories/{repository_id}` ## Acceptance Criteria - Board writers can attach/detach tracked repositories. - Board readers can list linked repositories. - Duplicate links are rejected or treated idempotently. - Tests cover access checks, duplicate behavior, and cross-organization rejection. ## Out Of Scope - Agent issue routes, Issue closing, Frontend UI.