Georg Dangl 9538842364 Use correct response code in push mirror creation response in v1_json.tmpl (#25476) ... In the process of doing a bit of automation via the API, we've discovered a _small_ issue in the Swagger definition. We tried to create a push mirror for a repository, but our generated client raised an exception due to an unexpected status code. When looking at this function: 3c7f5ed7b5/routers/api/v1/repo/mirror.go (L236-L240) We see it defines `201 - Created` as response: 3c7f5ed7b5/routers/api/v1/repo/mirror.go (L260-L262) But it actually returns `200 - OK`: 3c7f5ed7b5/routers/api/v1/repo/mirror.go (L373) So I've just updated the Swagger definitions to match the code😀 --------- Co-authored-by: Giteabot <teabot@gitea.io>		2023-06-28 22:00:19 +00:00
..
activitypub
admin	Refactor rename user and rename organization (#24052)	2023-05-21 23:13:47 +08:00
misc	Refactor web package and context package (#25298)	2023-06-18 09:59:09 +02:00
notify	Fix bugs related to notification endpoints (#25548)	2023-06-28 10:26:56 -04:00
org	Fix Permission in API returned repository struct (#25388)	2023-06-22 13:08:08 +00:00
packages	Add CRAN package registry (#22331)	2023-05-22 10:57:49 +08:00
repo	Use correct response code in push mirror creation response in v1_json.tmpl (#25476)	2023-06-28 22:00:19 +00:00
settings
swagger	API endpoint for changing/creating/deleting multiple files (#24887)	2023-05-29 17:41:35 +08:00
user	Fix Permission in API returned repository struct (#25388)	2023-06-22 13:08:08 +00:00
utils	New webhook trigger for receiving Pull Request review requests (#24481)	2023-05-24 22:06:27 -04:00
api.go	Fix bugs related to notification endpoints (#25548)	2023-06-28 10:26:56 -04:00
auth.go
auth_windows.go