Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-11385

Show that a rebase is still going, after a pull --rebase that caused conflicts

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • 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.

      At our company we use pull --rebase as default to avoid local merges when updating our dev branches. This usually works well.

      But if while rebasing the local commits a conflict happens, this leads to an visually unclear state. We can solve the conflict, but then it's not evident that a  git rebase --continue is needed to properly complete the pull!

      People sometimes continue on working on their code, not realising that they are still in the middle of the pull, and mess up their working copy.

      It would help a lot if the Pull button would indicate that the pull/rebase is not completed yet. Maybe it could change the text into "Continue Rebase"... Or display a warning / hint when conflicts are solved during a rebase.

       

      Thank you.

        1. 1Z0-976-dumps.pdf
          407 kB
          Harry Welch
        2. 3v0-752-Exam-Dumps-2019.pdf
          269 kB
          victoriavargas
        3. 400-351-Exam-Dumps-2019.pdf
          1.05 MB
          victoriavargas

              698877135425 Mukesh Kumar
              59d40ab6c702 Amedeo Amato
              Votes:
              6 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: