Display error message when creating new branch fails due to unmerged files #242

Activity

1. kuychaco

   added this to the 1: Staff Ship Git Integration milestone on Sep 11, 2016
2. simurai commented on Sep 14, 2016

   

   simurai

   on Sep 14, 2016

   Contributor

   More actions

   Just a thought.. there are probably tons of edge cases and errors. Would it make sense to have some kind of "catch all errors and show them as a message".

   • It would free us a bit from solving all these cases that happen sometimes, but are still not too common.
   • People reading those messages probably know what to do (well, if they are familiar using git with the command line).

   Similar to that output at the bottom of the git-control package, but not show it all the time and only when there is something we don't handle.

   

   👍React with 👍2Reacted by Ian Olsen and Katrina Uychaco
3. kuychaco commented on Sep 23, 2016

   

   kuychaco

   on Sep 23, 2016

   ContributorAuthor

   More actions

   @simurai yeah sounds reasonable. Currently we are catching errors and for certain ones we are displaying nicer, more readable versions of the error message. For errors that we're not doing this for, we should probably just display whatever git outputs to the command line.
4. kuychaco

   added

   bug

   branching

   on Sep 23, 2016
5. kuychaco

   closed this as completedin #286on Oct 26, 2016