YR Chen 7443a10fc3 Move from max( id ) to max( index ) for latest commit statuses (#30076) ... This PR replaces the use of `max( id )`, and instead using ``max( `index` )`` for determining the latest commit status. Building business logic over an `auto_increment` primary key like `id` is risky and there’re already plenty of discussions on the Internet. There‘s no guarantee for `auto_increment` values to be monotonic, especially upon failures or with a cluster. In the specific case, we met the problem of commit statuses being outdated when using TiDB as the database. As [being documented](https://docs.pingcap.com/tidb/stable/auto-increment), `auto_increment` values assigned to an `insert` statement will only be monotonic on a per server (node) basis. Closes #30074.		2024-03-28 16:01:15 +08:00
..
branch_list.go	Start to migrate from util.OptionalBool to optional.Option[bool] (#29329)	2024-02-23 02:18:33 +00:00
branch_test.go	Start to migrate from util.OptionalBool to optional.Option[bool] (#29329)	2024-02-23 02:18:33 +00:00
branch.go	Sync branches to DB immediately when handle git hook calling (#29493)	2024-03-06 16:47:52 +08:00
commit_status_test.go
commit_status.go	Move from max( id ) to max( index ) for latest commit statuses (#30076)	2024-03-28 16:01:15 +08:00
lfs_lock.go
lfs.go
main_test.go
protected_banch_list_test.go
protected_branch_list.go	Start to migrate from util.OptionalBool to optional.Option[bool] (#29329)	2024-02-23 02:18:33 +00:00
protected_branch_test.go
protected_branch.go
protected_tag_test.go
protected_tag.go