forked from Shiloh/githaven
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> |
||
|---|---|---|
| .. | ||
| admin.go | ||
| auth_form.go | ||
| org.go | ||
| package_form.go | ||
| repo_branch_form.go | ||
| repo_form_test.go | ||
| repo_form.go | ||
| repo_tag_form.go | ||
| runner.go | ||
| user_form_auth_openid.go | ||
| user_form_hidden_comments.go | ||
| user_form_test.go | ||
| user_form.go | ||