forgejo/tests/integration/migration-test
Earl Warren ff03a4eff6 chore: make migration tests relative to the root of the repository (#8999)
This is a noop refactor. It is on the path of each integration tests and this is why it needs no additional testing.

It makes it possible to run the migration tests using `go test` (which runs from the root) instead of building a test binary with `go test -c` that runs in the target directory, which is what the current tests are doing. This will be put to use to extract coverage in a unified way.

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/8999
Reviewed-by: jerger <jerger@noreply.codeberg.org>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>
2025-08-26 07:36:00 +02:00
..
gitea-v1.6.4.mysql.sql.gz feat: migrate TOTP secrets to keying 2024-11-27 00:34:16 +01:00
gitea-v1.6.4.postgres.sql.gz feat: migrate TOTP secrets to keying 2024-11-27 00:34:16 +01:00
gitea-v1.6.4.sqlite3.sql.gz feat: migrate TOTP secrets to keying 2024-11-27 00:34:16 +01:00
gitea-v1.7.0.mysql.sql.gz feat: migrate TOTP secrets to keying 2024-11-27 00:34:16 +01:00
gitea-v1.7.0.postgres.sql.gz feat: migrate TOTP secrets to keying 2024-11-27 00:34:16 +01:00
gitea-v1.7.0.sqlite3.sql.gz feat: migrate TOTP secrets to keying 2024-11-27 00:34:16 +01:00
migration_test.go chore: make migration tests relative to the root of the repository (#8999) 2025-08-26 07:36:00 +02:00