Giteabot 937996c74c Match api migration behavior to web behavior (#23552) (#23573) ... 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>		2023-03-19 15:30:02 +08:00
..
actions	Avoid panic caused by broken payload when creating commit status (#23216) (#23294)	2023-03-04 14:23:49 +00:00
packages	Notify on container image create (#22806)	2023-02-18 13:36:38 +08:00
v1	Match api migration behavior to web behavior (#23552) (#23573)	2023-03-19 15:30:02 +08:00