-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traverse continues after a failed push #1659
Comments
Huh it might be hard to circumvent... |
pls take a look at: I think we could provide a similar solution - notification-based, i.e.: GitPushResultNotification[] existingNotifications =
NotificationsManager.getNotificationsManager().getNotificationsOfType(GitPushResultNotification.class, myProject); then filter for |
Huh seems pretty hackish and brittle TBH 🤔 to rely on a notification to determine if an error has happened 🐞 |
It occurs to me that it's indeed what I observed recently (specifically, vanilla
git push
failing on non-fast-forward since the branch was present in the remote repo, but not inrefs/remotes
locally).I'd say it should NOT continue; the traverse flow should be stopped at any failure.
The text was updated successfully, but these errors were encountered: