Giteabot aa4bb37e92 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 09:21:17 +01:00
..
activitypub	Add context cache as a request level cache (#22294)	2023-02-15 21:37:34 +08:00
admin	Handle missing README in create repos API (#23387) (#23510)	2023-03-16 21:04:52 -04:00
misc	[BRANDING] Update nodeinfo branding	2023-03-18 18:19:04 +01:00
notify
org	Add loading yaml label template files (#22976) (#23232)	2023-03-01 21:57:34 -05:00
packages	Add Chef package registry (#22554)	2023-02-06 09:49:21 +08:00
repo	Match api migration behavior to web behavior (#23552) (#23573)	2023-03-19 09:21:17 +01:00
settings
swagger
user	Add scopes to API to create token and display them (#22989)	2023-02-20 15:28:44 -06:00
utils
api.go	[BRANDING] X-Forgejo-OTP can be used instead of X-Gitea-OTP	2023-03-18 18:19:05 +01:00
auth.go
auth_windows.go