mirror of
https://github.com/go-gitea/gitea.git
synced 2026-07-23 01:09:57 +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>
19 lines
615 B
Go
19 lines
615 B
Go
// Copyright 2024 The Gitea Authors. All rights reserved.
|
|
// SPDX-License-Identifier: MIT
|
|
|
|
package v1_22
|
|
|
|
import "gitea.dev/modelmigration/base"
|
|
|
|
func AddCommitStatusSummary(x base.EngineMigration) error {
|
|
type CommitStatusSummary struct {
|
|
ID int64 `xorm:"pk autoincr"`
|
|
RepoID int64 `xorm:"INDEX UNIQUE(repo_id_sha)"`
|
|
SHA string `xorm:"VARCHAR(64) NOT NULL INDEX UNIQUE(repo_id_sha)"`
|
|
State string `xorm:"VARCHAR(7) NOT NULL"`
|
|
}
|
|
// there is no migrations because if there is no data on this table, it will fall back to get data
|
|
// from commit status
|
|
return x.Sync(new(CommitStatusSummary))
|
|
}
|