Uploaded image for project: 'Sourcetree For Mac'
  1. Sourcetree For Mac
  2. SRCTREE-2999

Better feedback when rebase --continue is needed

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Git
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      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

              Unassigned Unassigned
              4261a27e4827 fritz
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: