Backend Issue 5: Add Backend Connection Validation API #6

New Issue

Closed

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

null commented

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

Owner

Goal

Let admins validate that a Forgejo connection and tracked repository are reachable before relying on sync.

Scope

Add validation endpoint for a connection.
Add validation endpoint for a tracked repository.
Use the Forgejo API client from Backend Issue 4.

Suggested Endpoints

POST /api/v1/forgejo/connections/{connection_id}/validate
POST /api/v1/forgejo/repositories/{repository_id}/validate

Acceptance Criteria

Connection validation confirms the configured base URL and token can make an authenticated API request.
Repository validation confirms owner/repo exists and token can read issue data.
Errors are safe for display and never include token values.
Tests cover success, bad token, missing repo, and remote timeout.

Out Of Scope

Issue sync, Frontend UI.

## Goal Let admins validate that a Forgejo connection and tracked repository are reachable before relying on sync. ## Scope - Add validation endpoint for a connection. - Add validation endpoint for a tracked repository. - Use the Forgejo API client from Backend Issue 4. ## Suggested Endpoints - `POST /api/v1/forgejo/connections/{connection_id}/validate` - `POST /api/v1/forgejo/repositories/{repository_id}/validate` ## Acceptance Criteria - Connection validation confirms the configured base URL and token can make an authenticated API request. - Repository validation confirms owner/repo exists and token can read issue data. - Errors are safe for display and never include token values. - Tests cover success, bad token, missing repo, and remote timeout. ## Out Of Scope - Issue sync, Frontend UI.