Github: Display error message when creating new branch fails due to unmerged files
➜ repo-merge-conflict-all git:(master) ✗ gco -b new branch
removed-on-master.txt: needs merge
error: you need to resolve your current index first
kuychaco
All 2 comments
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.
simurai
on 14 Sep 2016
👍2
@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.
kuychaco
on 23 Sep 2016
Was this page helpful?
0 / 5 - 0 ratings
Related issues
Ben3eeE
·
4Comments
jingr1
·
4Comments
danielbayley
·
5Comments
yubaoquan
·
3Comments
megaultrachicken
·
4Comments
Most helpful comment
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".
Similar to that output at the bottom of the
git-controlpackage, but not show it all the time and only when there is something we don't handle.