mirror of
1
Fork 0
forgejo/models/forgejo_migrations
Gergely Nagy 2bc226eb57
Drop Gitea-specific columns from two tables
Gitea and Forgejo chose to implement wiki branch naming differently, but
Forgejo picked the Gitea migration anyway, resulting in an unused column
in the database, which wasn't part of the `Repository` struct either -
something warned about during startup, too.

Similarly, Forgejo chose not to implement User badges at all - but kept
the existing code for it -, and the `badge` table ended up with an
unused `slug` column due to a Gitea migration, and resulted in another
warning at startup.

To keep the database consistent with the code, and to get rid of these
warnings, lets introduce a new migration, which simply drops these
Gitea-specific columns from the database.

Fixes #3463.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
2024-04-26 10:34:06 +02:00
..
v1_20 [SECURITY] Rework long-term authentication 2024-02-05 15:06:15 +01:00
v1_22 Do not update PRs based on events that happened before they existed 2024-04-11 11:16:23 +02:00
main_test.go [DB] Forgejo database migrations 2024-02-05 14:44:33 +01:00
migrate.go Drop Gitea-specific columns from two tables 2024-04-26 10:34:06 +02:00
migrate_test.go [DB] Forgejo database migrations 2024-02-05 14:44:33 +01:00
v13.go [FEAT]Add Option to hide Release Archive links (#3139) 2024-04-24 15:15:55 +00:00
v14.go Drop Gitea-specific columns from two tables 2024-04-26 10:34:06 +02:00