Split migration api endpoint into service specific one #14359

New Issue

GiteaMirror · 2025-11-02T11:10:48-06:00

GiteaMirror commented

2025-11-02 11:10:48 -06:00

Originally created by @TheFox0x7 on GitHub (Apr 10, 2025).

Feature Description

I think api could benefit from having a more narrow endpoints for migration. Instead of a single which has a lot of options - some irrelevant to the service chosen a service specific one would allow for better validation of the request as it can take service into account instead being generic.

My proposal is to add dedicated routes to /api/v1/repos/migrate/{service} endpoint (where service is a known migration source) and deprecate the generic endpoint.

This would also help users in understanding the endpoint - which options are supported and which aren't, instead of having to guess or go to UI to figure it out.

Screenshots

No response

Originally created by @TheFox0x7 on GitHub (Apr 10, 2025). ### Feature Description I think api could benefit from having a more narrow endpoints for migration. Instead of a single which has a lot of options - some irrelevant to the service chosen a service specific one would allow for better validation of the request as it can take service into account instead being generic. My proposal is to add dedicated routes to `/api/v1/repos/migrate/{service}` endpoint (where service is a known migration source) and deprecate the generic endpoint. This would also help users in understanding the endpoint - which options are supported and which aren't, instead of having to guess or go to UI to figure it out. ### Screenshots _No response_

GiteaMirror added the topic/api type/proposal labels 2025-11-02 11:10:48 -06:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14359