Skip to content

Commit eba3f0e

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 3f253b3 commit eba3f0e

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
@@ -154,7 +154,7 @@ func Migrate(ctx *context.APIContext) {
154154
Issues: form.Issues,
155155
Milestones: form.Milestones,
156156
Labels: form.Labels,
157-
Comments: true,
157+
Comments: form.Issues || form.PullRequests,
158158
PullRequests: form.PullRequests,
159159
Releases: form.Releases,
160160
GitServiceType: gitServiceType,

0 commit comments

Comments
 (0)