From 4b33afcd5bf08afa116512eaea92c73ade332bee Mon Sep 17 00:00:00 2001 From: zeripath Date: Thu, 29 Oct 2020 02:23:31 +0000 Subject: Migration failure during reaction migration from gitea (#13344) * Migrating reactions is just not that important A failure during migrating reactions should not cause failure of migration. Signed-off-by: Andrew Thornton * When checking issue reactions check the correct permission Signed-off-by: Andrew Thornton Co-authored-by: techknowlogick --- modules/migrations/migrate.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'modules/migrations/migrate.go') diff --git a/modules/migrations/migrate.go b/modules/migrations/migrate.go index 191f2a5550..3c505d82b6 100644 --- a/modules/migrations/migrate.go +++ b/modules/migrations/migrate.go @@ -69,7 +69,7 @@ func MigrateRepository(ctx context.Context, doer *models.User, ownerName string, } if err2 := models.CreateRepositoryNotice(fmt.Sprintf("Migrate repository from %s failed: %v", opts.OriginalURL, err)); err2 != nil { - log.Error("create respotiry notice failed: ", err2) + log.Error("create repository notice failed: ", err2) } return nil, err } -- cgit v1.2.3