Giteabot e6395e1e81 Handle invalid target when creating releases using API (#31841) (#32043) ...

Backport #31841 by @kemzeb

A 500 status code was thrown when passing a non-existent target to the
create release API. This snapshot handles this error and instead throws
a 404 status code.

Discovered while working on #31840.

Co-authored-by: Kemal Zebari <60799661+kemzeb@users.noreply.github.com>

2024-09-17 02:23:40 +00:00

..

e2e

Enable more revive linter rules (#30608)

2024-04-22 11:48:42 +00:00

fuzz

Rework markup link rendering (#26745)

2024-01-15 08:49:24 +00:00

gitea-lfs-meta

Test views of LFS files (#22196)

2022-12-23 07:41:56 +08:00

gitea-repositories-meta

Fix agit automerge (#31207) (#31881)

2024-08-20 16:20:58 +00:00

integration

Handle invalid target when creating releases using API (#31841) (#32043)

2024-09-17 02:23:40 +00:00

testdata/data/attachments/a/0

Allow get release download files and lfs files with oauth2 token format (#26430)

2023-10-01 10:41:52 +00:00

mssql.ini.tmpl

Disable query token param in integration tests (#28592)

2023-12-23 11:29:51 +08:00

mysql.ini.tmpl

Disable query token param in integration tests (#28592)

2023-12-23 11:29:51 +08:00

pgsql.ini.tmpl

Disable query token param in integration tests (#28592)

2023-12-23 11:29:51 +08:00

sqlite.ini.tmpl

Disable query token param in integration tests (#28592)

2023-12-23 11:29:51 +08:00

test_utils.go

Prevent update pull refs manually and will not affect other refs update (#31931) (#31955)

2024-09-02 18:28:00 +08:00