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
Adding any kind of state to VB is undesirable, but we could have a periodic check of attached repos and their open PRs, and for any where VB has a 'pending' state, we could scan the worker queue and if not lined up for a change, enforce a status check. This would unblock any PRs should VB have failed previously due to environment/runtime issues.
On Mon, Jul 17, 2017 at 9:19 AM, Heds Simons ***@***.***> wrote:
This occurred recently: https://www.flowdock.com/app/
rulemotion/resin-devops/threads/H4lzkd9F0b_QWPGErVLPSPmLlp4
Adding any kind of state to VB is undesirable, but we could have a
periodic check of attached repos and their open PRs, and for any where VB
has a 'pending' state, we could scan the worker queue and if not lined up
for a change, enforce a status check. This would unblock any PRs should VB
have failed previously due to environment/runtime issues.
cc @brownjohnf <https://github.com/brownjohnf>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#196>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA9GWUlXj7bF2SOoi1ElZ7PtENyAnYmlks5sO4mAgaJpZM4OaLn2>
.
This occurred recently: https://www.flowdock.com/app/rulemotion/resin-devops/threads/H4lzkd9F0b_QWPGErVLPSPmLlp4
Adding any kind of state to VB is undesirable, but we could have a periodic check of attached repos and their open PRs, and for any where VB has a 'pending' state, we could scan the worker queue and if not lined up for a change, enforce a status check. This would unblock any PRs should VB have failed previously due to environment/runtime issues.
cc @brownjohnf
The text was updated successfully, but these errors were encountered: