Closed
Description
Description
If i try to update an issue via:
curl --location --request PATCH 'http://localhost:3000/api/v1/repos/root/test/issues/1' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer ***' \
--data '{
"assignees": [],
"body": "Test 123",
"title": "Dependency Dashboard",
"state": "open"
}'
The issue is updated just fine but Gitea returns status code 500.
The problem here is the state field. Without the state field everything works just fine.
I think the problem was introduced with a50026e#diff-f33622667aa80c1735ccaef8e7331422504e8c449f691c6847ec4f6737a278cd. @yp05327 maybe you can have a look at it.
The problem occured because Renovate Bot useses the state field in its model (see https://github.com/renovatebot/renovate/blob/main/lib/modules/platform/gitea/types.ts#L171-L176) for issue creation / update via the Gitea API.
Gitea Version
1.22.1
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
The logs:
2024/08/19 07:11:13 ...api/v1/repo/issue.go:894:EditIssue() [E] ChangeStatus: Issue [1] 0 was already closed
2024/08/19 07:11:13 ...eb/routing/logger.go:102:func1() [I] router: completed PATCH /api/v1/repos/root/test/issues/1 for 172.17.0.1:36648, 500 Internal Server Error in 33.5ms @ repo/issue.go:742(repo.EditIssue)
The API returns:
{
"message": "Issue [1] 0 was already closed",
"url": "http://localhost:3000/api/swagger"
}
Git Version
No response
Operating System
No response
How are you running Gitea?
Docker
Database
SQLite