• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Highest Highest
    • None
    • 2.3.1
    • Git
    • Main project and submodule

    • Severity 2 - Major

      In my project I have a submodule. I can open it with a double click but I can't browse the diff file or I can't commit...
      sone thing that strange when I look the file path's submodule, it look like "../../../myfile.c" for exemple.

            [SRCTREE-4142] Can't access to submodule

            Fix for this issue is available in Sourcetree 4.2.2

            Raman Sidarakin (Inactive) added a comment - Fix for this issue is available in Sourcetree 4.2.2

            This is still an issue in SourceTree 4.0.2 (236). It happens when the submodule directory name is equal to one of the directory names in the root directory / such as Library, System or Users.

            SourceTree is unable to show a diff for files in these submodules (the diff pane keeps showing a spinner), the path shows as ../../../users/README.txt and when I click "Log Selected..." I receive a warning: "Potential security issue detected in the specified URL".

            Joost-Wim Boekesteijn added a comment - This is still an issue in SourceTree 4.0.2 (236). It happens when the submodule directory name is equal to one of the directory names in the root directory / such as Library , System or Users . SourceTree is unable to show a diff for files in these submodules (the diff pane keeps showing a spinner), the path shows as ../../../users/README.txt and when I click "Log Selected..." I receive a warning: "Potential security issue detected in the specified URL".

            This appears to only happen when the submodule is stored in a folder directly off the root of the parent repo. So, if I have my parent stored in ~/project, and create a submodule at ~/project/library, Sourcetree will fail to execute properly most functions due, sometimes complaining about the path, sometimes silently failing. If the library was unde ~/project/folder/library, it would work fine.

            I'm using Version 2.7.1 (159)

            Christopher George added a comment - This appears to only happen when the submodule is stored in a folder directly off the root of the parent repo. So, if I have my parent stored in ~/project, and create a submodule at ~/project/library, Sourcetree will fail to execute properly most functions due, sometimes complaining about the path, sometimes silently failing. If the library was unde ~/project/folder/library, it would work fine. I'm using Version 2.7.1 (159)

              Unassigned Unassigned
              b71645ead99a Philippe Fouquet
              Affected customers:
              5 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: