forked from gitea/gitea
e7c2231dee
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> |
||
|---|---|---|
| .. | ||
| webhook | ||
| actions.tmpl | ||
| branches.tmpl | ||
| collaboration.tmpl | ||
| deploy_keys.tmpl | ||
| githook_edit.tmpl | ||
| githooks.tmpl | ||
| layout_footer.tmpl | ||
| layout_head.tmpl | ||
| lfs.tmpl | ||
| lfs_file.tmpl | ||
| lfs_file_find.tmpl | ||
| lfs_locks.tmpl | ||
| lfs_pointers.tmpl | ||
| nav.tmpl | ||
| navbar.tmpl | ||
| options.tmpl | ||
| protected_branch.tmpl | ||
| runner_edit.tmpl | ||
| secrets.tmpl | ||
| tags.tmpl | ||