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
{{ message }}
This repository has been archived by the owner on Aug 29, 2023. It is now read-only.
Automerge keeps a runner occupied for as long as there are any outstanding checks on a PR. This could lead to starvation if automerge workflows get scheduled on all the runners. We haven't hit this yet but I saw cases where half the runners where automerge workflows.
Maybe we could periodically go through all the web3-bot PRs and merge them if all the checks are passing instead?
The text was updated successfully, but these errors were encountered:
Automerge keeps a runner occupied for as long as there are any outstanding checks on a PR. This could lead to starvation if automerge workflows get scheduled on all the runners. We haven't hit this yet but I saw cases where half the runners where automerge workflows.
Maybe we could periodically go through all the web3-bot PRs and merge them if all the checks are passing instead?
The text was updated successfully, but these errors were encountered: