Giteabot efe7561787 Match api migration behavior to web behavior (#23552) (#23572) ... 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:29:57 +08:00
..
api	Match api migration behavior to web behavior (#23552) (#23572)	2023-03-19 15:29:57 +08:00
common	Add support for HEAD requests in Maven registry (#21834) (#21929)	2022-11-25 13:46:28 +02:00
install	Provide the ability to set password hash algorithm parameters (#22942) (#22943)	2023-02-19 15:35:52 +08:00
private	Fix missing message in git hook when pull requests disabled on fork (#22625) (#22658)	2023-01-30 08:55:45 +08:00
utils	refactor webhook *NewPost (#20729)	2022-08-11 17:48:23 +02:00
web	Make branches list page operations remember current page (#23420) (#23459)	2023-03-15 13:13:27 +01:00
init.go	Sync git hooks when config file path changed (#21619) (#21626)	2022-10-30 11:17:11 +08:00