Zettat123 e7c2231dee Support for status check pattern (#24633) ... This PR is to allow users to specify status checks by patterns. Users can enter patterns in the "Status Check Pattern" `textarea` to match status checks and each line specifies a pattern. If "Status Check" is enabled, patterns cannot be empty and user must enter at least one pattern. Users will no longer be able to choose status checks from the table. But a __*`Matched`*__ mark will be added to the matched checks to help users enter patterns. Benefits: - Even if no status checks have been completed, users can specify necessary status checks in advance. - More flexible. Users can specify a series of status checks by one pattern. Before:  After:  --------- Co-authored-by: silverwind <me@silverwind.io>		2023-05-17 16:11:13 +08:00
..
check.go	Rewrite queue (#24505)	2023-05-08 19:49:59 +08:00
check_test.go	Rewrite queue (#24505)	2023-05-08 19:49:59 +08:00
comment.go	Make more functions use ctx instead of db.DefaultContext (#24068)	2023-04-14 14:18:28 -04:00
commit_status.go	Support for status check pattern (#24633)	2023-05-17 16:11:13 +08:00
edits.go
lfs.go
main_test.go
merge.go
merge_merge.go
merge_prepare.go
merge_rebase.go
merge_squash.go	Improve squash merge commit author and co-author with private emails (#22977)	2023-03-09 22:17:04 -05:00
merge_test.go
patch.go
patch_unmerged.go
pull.go	Refresh the refernce of the closed PR when reopening (#24231)	2023-05-08 14:39:32 +08:00
pull_test.go
review.go	Make more functions use ctx instead of db.DefaultContext (#24068)	2023-04-14 14:18:28 -04:00
temp_repo.go
update.go
update_rebase.go