forgejo/models/git
caicandong 840830b655
Remove commit status running and warning to align GitHub (#25839)
Fix #25776. Close #25826.

In the discussion of #25776, @wolfogre's suggestion was to remove the
commit status of `running` and `warning` to keep it consistent with
github.

references:
-
https://docs.github.com/en/rest/commits/statuses?apiVersion=2022-11-28#about-commit-statuses


## ⚠️ BREAKING ⚠️

So the commit status of Gitea will be consistent with GitHub, only
`pending`, `success`, `error` and `failure`, while `warning` and
`running` are not supported anymore.

---------

Co-authored-by: Jason Song <i@wolfogre.com>
2023-07-21 16:24:36 +08:00
..
branch.go Exclude default branch from pushed branch hint (#25795) 2023-07-10 11:18:55 +00:00
branch_list.go Make FindBranches have stable result (#25631) 2023-07-03 04:11:32 +00:00
branch_test.go Fix branch commit message too long problem (#25588) 2023-06-30 17:03:05 +08:00
commit_status.go Display branch commit status (#25608) 2023-07-03 03:32:21 +00:00
commit_status_test.go Remove commit status running and warning to align GitHub (#25839) 2023-07-21 16:24:36 +08:00
lfs.go Replace interface{} with any (#25686) 2023-07-04 18:36:08 +00:00
lfs_lock.go Introduce path Clean/Join helper functions (#23495) 2023-03-21 16:02:49 -04:00
main_test.go
protected_banch_list_test.go Fix branch protection priority (#24045) 2023-04-11 13:22:49 -04:00
protected_branch.go Rename repo.GetOwner to repo.LoadOwner (#22967) 2023-02-18 20:11:03 +08:00
protected_branch_list.go Sync branches into databases (#22743) 2023-06-29 10:03:20 +00:00
protected_branch_test.go
protected_tag.go
protected_tag_test.go