Better feedback when rebase --continue is needed

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: Git
    • None

      Hi, thanks for the free tool.

      If I make a git rebase, and there is a conflict, the repo is in 'limbo' until I resolve the conflict AND FINISH THE REBASE. But after resolving the conflict and just by looking at SourceTree it all appears normal. In fact I have to go to the CLI to do

      git rebase --continue

      (or abort or whatever). If I need to go to the CLI it means SourceTree is failing.

      Suggestion:

      • color code the UI, or somehow visually indicate that the rebase is not complete
      • add rebase continue / abort / skip button(s)
      • disable all other buttons

      Thanks

            Assignee:
            Unassigned
            Reporter:
            fritz
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: