forgejo-federation/routers/api
Gusted 938a450c9e
[GITEA] Document correct status code for creating Tag
- When there's a succesful POST operation, it should return a 201 status
code (which is the status code for succesful created) and additionally
the created object.
- Currently for the `POST /repos/{owner}/{repo}/tags` endpoint an 200
status code was documented in the OpenAPI specification, while an 201
status code was actually being returned. In this case the code is
correct and the documented status code needs to be adjusted.
- Resolves #2200

(cherry picked from commit a2939116f5ce21295981a3a9aa84a73fe289b8b2)
(cherry picked from commit 22cff4158564a3e69bef83c458cf1f129e1b688b)
(cherry picked from commit b23a7f27bb10e782e70530cc8c37f5d11f7a684a)
2024-02-05 16:09:43 +01:00
..
actions Add artifacts v4 jwt to job message and accept it (#28885) 2024-02-02 14:25:59 +00:00
forgejo/v1 [CLEANUP] Reuse ForgejoVersion variable 2024-02-05 14:45:11 +01:00
packages [GITEA] Drop sha256-simd in favor of stdlib 2024-02-05 16:09:40 +01:00
v1 [GITEA] Document correct status code for creating Tag 2024-02-05 16:09:43 +01:00