forgejo/models/migrations
Gusted e8c1bfc2e5
[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

(cherry picked from commit 8e02be7e89a76ccbc3f8a58577be0fcc34e1469e)
(cherry picked from commit 006f06441645d864fc27ca30352367b3afafc5bb)
2024-02-05 13:33:59 +01:00
..
base
fixtures [CI] Fix false positive in database migration 2024-02-05 13:33:59 +01:00
v1_6
v1_7
v1_8
v1_9
v1_10
v1_11
v1_12
v1_13
v1_14
v1_15
v1_16
v1_17
v1_18 Refactor system setting (#27000) 2023-10-05 09:08:19 +08:00
v1_19
v1_20
v1_21 handle repository.size column being NULL in migration v263 (#28336) 2023-12-05 14:31:13 +00:00
v1_22 [CI] Fix false positive in database migration 2024-02-05 13:33:59 +01:00
migrations.go Add support for sha256 repositories (#23894) 2024-01-19 17:05:02 +01:00