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
..
api	Use correct response code in push mirror creation response in v1_json.tmpl (#25476)	2023-06-28 22:00:19 +00:00
common	Use fetch to send requests to create issues/comments (#25258)	2023-06-16 06:32:43 +00:00
install	Remove "CHARSET" config option for MySQL, always use "utf8mb4" (#25413)	2023-06-21 10:49:25 +00:00
private	Use the type RefName for all the needed places and fix pull mirror sync bugs (#24634)	2023-05-26 01:04:48 +00:00
utils	Implement FSFE REUSE for golang files (#21840)	2022-11-27 18:20:29 +00:00
web	Use JSON response for "user/logout" (#25522)	2023-06-26 21:36:10 +02:00
init.go	Refactor path & config system (#25330)	2023-06-21 13:50:26 +08:00