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
If you kill the deploy somewhere between the initiation and completion of an action, the deploy summary printed will be inaccurate. For example, if you abort the deploy between the predeploy and the main deploy, the summary will say "No actions taken". Ideas for solutions:
Introduce a mechanism for tracking the action currently being attempted and reporting it on failure
Don't print the summary section when the process has been killed
Change the message printed to be more ¯\_(ツ)_/¯
The text was updated successfully, but these errors were encountered:
#244 definitely implemented (2) . The UX would be better if we'd done (1) but it hasn't come up so I think we can close this out and re-open if it comes up again.
If you kill the deploy somewhere between the initiation and completion of an action, the deploy summary printed will be inaccurate. For example, if you abort the deploy between the predeploy and the main deploy, the summary will say "No actions taken". Ideas for solutions:
The text was updated successfully, but these errors were encountered: