forgejo-backport-action 80476238ab [v15.0/forgejo] fix: cleanup data before migration retry (#12422) ... **Backport:** https://codeberg.org/forgejo/forgejo/pulls/12370 In the case you hit some API error (Github ratelimit was often a problem) or the instance restarted in the middle of your migration, you would be left with data on the disk and/or database. Upon retrying the migration the migration code would (rightfully) fail because it's trying to migrate stuff that already exists. This was hit so often on Codeberg it was better to force people to delete and start whole migration process again: 28ee60c91f Delete the repository data before retrying to solve this. Co-authored-by: Gusted <postmaster@gusted.xyz> Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/12422		2026-05-06 15:31:51 +02:00
..
cron.go	chore: branding import path (#7337)	2025-03-27 19:40:14 +00:00
setting.go	feat: auto cleanup of offline runners (#7803)	2025-06-08 00:13:37 +02:00
tasks.go	[v15.0/forgejo]: chore: add modernizer linter (#11949)	2026-04-02 16:54:46 +02:00
tasks_actions.go	fix: garbage collect lingering actions logs (#10009)	2025-11-18 18:59:01 +01:00
tasks_basic.go	chore: branding import path (#7337)	2025-03-27 19:40:14 +00:00
tasks_extended.go	[v15.0/forgejo] fix: cleanup data before migration retry (#12422)	2026-05-06 15:31:51 +02:00
tasks_extended_test.go	fix: LFS GC is never running because of a bug in the parsing of the INI file (#9202)	2025-09-09 22:32:49 +02:00
tasks_test.go	Add testifylint to lint checks (#4535)	2024-07-30 19:41:10 +00:00