diff options
| author | Giteabot <teabot@gitea.io> | 2023-03-19 03:29:57 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-19 15:29:57 +0800 |
| commit | efe756178708ffa22f76f4e87afb226978f54360 (patch) | |
| tree | b41b5354418065e4d7a47ec8531885ab40bd3c70 | |
| parent | e01e78a9471a9147fc50860b50196b6cebfb5d06 (diff) | |
| download | gitea-release/v1.18.tar.gz gitea-release/v1.18.zip | |
Match api migration behavior to web behavior (#23552) (#23572)release/v1.18
Backport #23552 by @atomaka
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: Andrew Tomaka <atomaka@atomaka.com>
Co-authored-by: Lauris BH <lauris@nix.lv>
Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
| -rw-r--r-- | routers/api/v1/repo/migrate.go | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/routers/api/v1/repo/migrate.go b/routers/api/v1/repo/migrate.go index ed371d787c..ecfbb1e45b 100644 --- a/routers/api/v1/repo/migrate.go +++ b/routers/api/v1/repo/migrate.go @@ -155,7 +155,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, |