Skip to content

Commit 61bd19d

Browse files
atomakalafrikslunny
authored andcommitted
Match api migration behavior to web behavior (go-gitea#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 <[email protected]> Co-authored-by: Lunny Xiao <[email protected]>
1 parent e01e78a commit 61bd19d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

routers/api/v1/repo/migrate.go

+1-1
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ func Migrate(ctx *context.APIContext) {
155155
Issues: form.Issues,
156156
Milestones: form.Milestones,
157157
Labels: form.Labels,
158-
Comments: true,
158+
Comments: form.Issues || form.PullRequests,
159159
PullRequests: form.PullRequests,
160160
Releases: form.Releases,
161161
GitServiceType: gitServiceType,

0 commit comments

Comments
 (0)