mirror of
https://github.com/go-gitea/gitea.git
synced 2026-07-23 13:37:38 +02:00
fff32e9469
Migrations should never use model structs directly, because the model structs can be different in different releases. e.g. if one migration uses "User" model, it works in the early releases, then one day, when the User model changes, the migration breaks because it will use the new (incorrect) User model, it should only use the old User model. The same to "modules/structs". --------- Signed-off-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: delvh <dev.lh@web.de>
28 lines
560 B
Go
28 lines
560 B
Go
// Copyright 2024 The Gitea Authors. All rights reserved.
|
|
// SPDX-License-Identifier: MIT
|
|
|
|
package v1_24
|
|
|
|
import (
|
|
"gitea.dev/modelmigration/base"
|
|
|
|
"xorm.io/xorm"
|
|
)
|
|
|
|
type pullAutoMerge struct {
|
|
DeleteBranchAfterMerge bool
|
|
}
|
|
|
|
// TableName return database table name for xorm
|
|
func (pullAutoMerge) TableName() string {
|
|
return "pull_auto_merge"
|
|
}
|
|
|
|
func AddDeleteBranchAfterMergeForAutoMerge(x base.EngineMigration) error {
|
|
_, err := x.SyncWithOptions(xorm.SyncOptions{
|
|
IgnoreConstrains: true,
|
|
IgnoreIndices: true,
|
|
}, new(pullAutoMerge))
|
|
return err
|
|
}
|