forgejo/routers/api/v1
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 Add context cache as a request level cache (#22294) 2023-02-15 21:37:34 +08:00
admin Add login name and source id for admin user searching API (#23376) 2023-03-15 19:53:01 +08:00
misc Implement FSFE REUSE for golang files (#21840) 2022-11-27 18:20:29 +00:00
notify Move convert package to services (#22264) 2022-12-29 10:57:15 +08:00
org Add user webhooks (#21563) 2023-03-10 08:28:32 -06:00
packages Add Swift package registry (#22404) 2023-03-13 15:28:39 -05:00
repo Match api migration behavior to web behavior (#23552) 2023-03-19 02:29:14 -04:00
settings Implement FSFE REUSE for golang files (#21840) 2022-11-27 18:20:29 +00:00
swagger add user rename endpoint to admin api (#22789) 2023-03-14 03:45:21 -04:00
user Use context for RepositoryList.LoadAttributes (#23435) 2023-03-13 11:31:41 +00:00
utils Add user webhooks (#21563) 2023-03-10 08:28:32 -06:00
api.go Add login name and source id for admin user searching API (#23376) 2023-03-15 19:53:01 +08:00
auth.go Implement FSFE REUSE for golang files (#21840) 2022-11-27 18:20:29 +00:00
auth_windows.go Implement FSFE REUSE for golang files (#21840) 2022-11-27 18:20:29 +00:00