We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
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

    • 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
        2. 3v0-752-Exam-Dumps-2019.pdf
          269 kB
        3. 400-351-Exam-Dumps-2019.pdf
          1.05 MB
        4. image-2024-12-26-17-29-48-851.png
          image-2024-12-26-17-29-48-851.png
          157 kB

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            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

              • 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
                  2. 3v0-752-Exam-Dumps-2019.pdf
                    269 kB
                  3. 400-351-Exam-Dumps-2019.pdf
                    1.05 MB
                  4. image-2024-12-26-17-29-48-851.png
                    image-2024-12-26-17-29-48-851.png
                    157 kB

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

                          Created:
                          Updated:
                          Resolved:

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

                              Created:
                              Updated:
                              Resolved: