Earl Warren 9f1302f685 fix(api): issue state change is not idempotent ... The PATCH if issue & pull request switched to use the service functions instead. However, the service function changing the state is not idempotent. Instead of doing nothing which changing from open to open or close to close, it will fail with an error like: Issue [2472] 0 was already closed Regression of: 6a4bc0289d Fixes: https://codeberg.org/forgejo/forgejo/issues/4686 (cherry picked from commit e9e3b8c0f3)		2024-07-25 14:21:00 +00:00
..
e2e	Merge branch 'v7.0/forgejo' into bp-v7.0/forgejo-e3665c3	2024-07-14 19:32:30 +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	tests(integration): add TestPullMergeBranchProtect	2024-06-02 22:05:08 +02:00
integration	fix(api): issue state change is not idempotent	2024-07-25 14:21:00 +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	[CI] Forgejo Actions based CI (squash) all queues are immediate	2024-02-05 13:33:59 +01:00
mysql.ini.tmpl	[CI] Forgejo Actions based CI (squash) all queues are immediate	2024-02-05 13:33:59 +01:00
pgsql.ini.tmpl	[CI] Forgejo Actions based CI (squash) all queues are immediate	2024-02-05 13:33:59 +01:00
sqlite.ini.tmpl	[TESTS] increase test-sqlite log level to Trace	2024-02-05 14:44:33 +01:00
test_utils.go	fix(tests): 30s to cancel processes to avoid false negatives	2024-04-19 17:04:53 +02:00