Backend Issue 3: Add Admin Tracked Repository CRUD API #4

New Issue

Closed

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

null commented

2026-05-19 02:27:58 -05:00

Owner

Goal

Allow organization admins to register Forgejo repositories that Pipeline should track.

Scope

Add repository schemas.
Add admin-only list/create/read/update/delete endpoints for tracked repositories.
Validate the selected connection belongs to the caller's organization.
Do not sync issues in this issue.

Suggested Endpoints

GET /api/v1/forgejo/repositories
POST /api/v1/forgejo/repositories
GET /api/v1/forgejo/repositories/{repository_id}
PATCH /api/v1/forgejo/repositories/{repository_id}
DELETE /api/v1/forgejo/repositories/{repository_id}

Acceptance Criteria

Admins can manage tracked repositories.
Duplicate active repository records for the same organization/connection/owner/repo are rejected.
Tests cover CRUD, duplicate rejection, and cross-organization connection rejection.

Out Of Scope

Issue cache, sync, board links, Frontend UI.

## Goal Allow organization admins to register Forgejo repositories that Pipeline should track. ## Scope - Add repository schemas. - Add admin-only list/create/read/update/delete endpoints for tracked repositories. - Validate the selected connection belongs to the caller's organization. - Do not sync issues in this issue. ## Suggested Endpoints - `GET /api/v1/forgejo/repositories` - `POST /api/v1/forgejo/repositories` - `GET /api/v1/forgejo/repositories/{repository_id}` - `PATCH /api/v1/forgejo/repositories/{repository_id}` - `DELETE /api/v1/forgejo/repositories/{repository_id}` ## Acceptance Criteria - Admins can manage tracked repositories. - Duplicate active repository records for the same organization/connection/owner/repo are rejected. - Tests cover CRUD, duplicate rejection, and cross-organization connection rejection. ## Out Of Scope - Issue cache, sync, board links, Frontend UI.