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

SourceTree does not delete submodule files when pulling a submodule removal

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Low Low
    • None
    • 1.3.3, 3.1.3
    • Git
    • None

      Step to reproduce:

      • Have a git repo with a submodule checked out
      • from another client, remove, commit and push the submodule removal
      • from the first client, pull the changes (we have "Use rebase instead of merge by default for tracked branches" On here, not sure if it's relevant or not)

      Expected result:
      All the files of the submodule are gone if there is no uncommited/pushed change, a warning otherwise

      Actual result:
      The submodule is gone in SourceTree GUI, but the files are still present on disk. SourceTree does not suggest this files as new files for a commit. This files are hidden in the GUI

      Also, the submodule data is still in .git\modules*, and cause trouble if you want to replace a submodule by another with the same name, or simply change the URL.

            [SRCTREEWIN-1330] SourceTree does not delete submodule files when pulling a submodule removal

            K. Yamamoto made changes -
            Link New: This issue is related to SRCTREEWIN-937 [ SRCTREEWIN-937 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: JAC Bug Workflow v3 [ 3453259 ] New: SRCTREE JAC Bug Workflow [ 3743136 ]
            Ai Hirama made changes -
            Affects Version/s New: 3.1.3 [ 86495 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: SourceTree Bug Workflow [ 589961 ] New: JAC Bug Workflow v3 [ 3453259 ]
            minnsey made changes -
            Resolution New: Obsolete [ 11 ]
            Status Original: Open [ 1 ] New: Closed [ 6 ]
            Michael Muré created issue -

              sstreeting Steve Streeting (Inactive)
              michael.mure Michael Muré
              Affected customers:
              2 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: