You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're increasing our adoption of GitHub Actions, now they're free for use in public repos across all orgs and we've ratified RFC 123.
Currently, this tool doesn't configure any of the GitHub Actions status checks to be "required", only Jenkins, which means that we have to manually enable the correct status checks, which wastes developer time.
We should make it so that if Actions config is present in the repo (we're standardising on .github/workflows/ci.yml as the file path), we configure those status checks as required. As an overrideable option, we should be able to specify "strict" checks (that is, branches must be up-to-date with master before being mergeable) for repos.
The text was updated successfully, but these errors were encountered:
We're increasing our adoption of GitHub Actions, now they're free for use in public repos across all orgs and we've ratified RFC 123.
Currently, this tool doesn't configure any of the GitHub Actions status checks to be "required", only Jenkins, which means that we have to manually enable the correct status checks, which wastes developer time.
We should make it so that if Actions config is present in the repo (we're standardising on
.github/workflows/ci.yml
as the file path), we configure those status checks as required. As an overrideable option, we should be able to specify "strict" checks (that is, branches must be up-to-date withmaster
before being mergeable) for repos.The text was updated successfully, but these errors were encountered: