gitea/routers
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
..
api Match api migration behavior to web behavior (#23552) 2023-03-19 02:29:14 -04:00
common Support sanitising the URL by removing extra slashes in the URL (#21333) 2023-03-04 21:31:24 +08:00
install Set X-Gitea-Debug header once (#23361) 2023-03-08 15:40:04 -05:00
private Use context parameter in services/repository (#23186) 2023-02-28 16:17:51 -06:00
utils Implement FSFE REUSE for golang files (#21840) 2022-11-27 18:20:29 +00:00
web Do not store user projects as organization projects (#23353) 2023-03-17 21:07:23 +08:00
init.go Refactor setting.Database.UseXXX to methods (#23354) 2023-03-07 18:51:06 +08:00