Andrew Tomaka 0206882e8a Match api migration behavior to web behavior (#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 <lauris@nix.lv> Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>		2023-03-19 02:29:14 -04:00
..
activitypub
admin	Add login name and source id for admin user searching API (#23376)	2023-03-15 19:53:01 +08:00
misc
notify
org
packages
repo	Match api migration behavior to web behavior (#23552)	2023-03-19 02:29:14 -04:00
settings
swagger
user
utils
api.go	Add login name and source id for admin user searching API (#23376)	2023-03-15 19:53:01 +08:00
auth_windows.go
auth.go