gitea

You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

History

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>		2 years ago
..
activitypub	Add context cache as a request level cache (#22294 )	2 years ago
admin	Add login name and source id for admin user searching API (#23376 )	2 years ago
misc	Implement FSFE REUSE for golang files (#21840 )	2 years ago
notify	Move `convert` package to services (#22264 )	2 years ago
org	Add user webhooks (#21563 )	2 years ago
packages	Add Swift package registry (#22404 )	2 years ago
repo	Match api migration behavior to web behavior (#23552 )	2 years ago
settings	Implement FSFE REUSE for golang files (#21840 )	2 years ago
swagger	add user rename endpoint to admin api (#22789 )	2 years ago
user	Use context for `RepositoryList.LoadAttributes` (#23435 )	2 years ago
utils	Add user webhooks (#21563 )	2 years ago
api.go	Add login name and source id for admin user searching API (#23376 )	2 years ago
auth.go	Implement FSFE REUSE for golang files (#21840 )	2 years ago
auth_windows.go	Implement FSFE REUSE for golang files (#21840 )	2 years ago