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
The deploy failure alerts are incredible useful, but it would be nice for there to be way of knowing if the problem is still ongoing. This could mean replying to the thread when the pipeline is unpaused (assuming it was paused) or providing engineers with a means of marking the problem as resolved. The latter would also enable us to have engineers let us know if an alert was a flake which could prove useful, but this is out of scope for now.
The text was updated successfully, but these errors were encountered:
The deploy failure alerts are incredible useful, but it would be nice for there to be way of knowing if the problem is still ongoing. This could mean replying to the thread when the pipeline is unpaused (assuming it was paused) or providing engineers with a means of marking the problem as resolved. The latter would also enable us to have engineers let us know if an alert was a flake which could prove useful, but this is out of scope for now.
The text was updated successfully, but these errors were encountered: