From eba3f0e37dabe6f5d21352d3e61be10080611e0e Mon Sep 17 00:00:00 2001 From: Andrew Tomaka Date: Sun, 19 Mar 2023 02:29:14 -0400 Subject: [PATCH] Match api migration behavior to web behavior (#23552) When attempting to migrate a repository via the API endpoint comments are always included. This can create a problem if your source repository has issues or pull requests but you do not want to import them into Gitea that displays as something like: > Error 500: We were unable to perform the request due to server-side problems. 'comment references non existent IssueIndex 4 There are only two ways to resolve this: 1. Migrate using the web interface 2. Migrate using the API including at issues or pull requests. This PR matches the behavior of the API migration router to the web migration router. Co-authored-by: Lauris BH Co-authored-by: Lunny Xiao --- routers/api/v1/repo/migrate.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/routers/api/v1/repo/migrate.go b/routers/api/v1/repo/migrate.go index 09e857b5fcfe8..efce39e520344 100644 --- a/routers/api/v1/repo/migrate.go +++ b/routers/api/v1/repo/migrate.go @@ -154,7 +154,7 @@ func Migrate(ctx *context.APIContext) { Issues: form.Issues, Milestones: form.Milestones, Labels: form.Labels, - Comments: true, + Comments: form.Issues || form.PullRequests, PullRequests: form.PullRequests, Releases: form.Releases, GitServiceType: gitServiceType,