Gusted 8e02be7e89 [CI] Fix false positive in database migration ... - This also means that if one of the test fails, it will actually propagate to make and subsequently fail the test. - Remove the 'delete duplicates issue users' code, I checked this against my local development database (which contains quite bizarre cases, even some that Forgejo does not like), my local instance database and against Codeberg production and they all yielded no results to this query, so I'm removing it thus resolving the error that the delete code was not compatible with Mysql. - Sync all tables that are requires by the migration in the test. - Resolves #2206		2024-01-23 19:47:35 +01:00
..
main_test.go	Add combined index for issue_user.uid and issue_id (#28080)	2023-12-14 09:26:59 +00:00
v280.go	Rename the default themes to gitea-light, gitea-dark, gitea-auto (#27419)	2023-10-06 09:46:36 +02:00
v281.go	Enhanced auth token / remember me (#27606)	2023-10-14 00:56:41 +00:00
v282.go	Add Index to pull_auto_merge.doer_id (#27811)	2023-10-30 08:39:29 +00:00
v283.go	[CI] Fix false positive in database migration	2024-01-23 19:47:35 +01:00
v283_test.go	Fix migration test (#28659)	2023-12-30 21:54:48 +08:00
v284.go	Add branch protection setting for ignoring stale approvals (#28498)	2024-01-15 07:20:01 +00:00
v285.go	Fix incorrect action duration time when rerun the job before executed once (#28364)	2024-01-19 14:05:49 +00:00
v286.go	Add support for sha256 repositories (#23894)	2024-01-19 17:05:02 +01:00
v286_test.go	[CI] Fix false positive in database migration	2024-01-23 19:47:35 +01:00