SourceTree incorrectly reports that a file is not tracked for Git LFS.

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 3.2.4
    • Component/s: Git
    • None
    • Severity 2 - Major

      Environment

      • SourceTree Version: 3.2.6

      Steps To Reproduce

      1. Clone a repository that already has Git LFS enabled.
      2. Open a terminal console.
      3. Enable Git LFS hooks via: git lfs install
      4. Create a new case-insensitive filter.
        • For example: git lfs track "*.[Zz][Ii][Pp]"
        • After this change, Source Tree should be reporting that .gitattributes has changed.
          • If not, then ensure that Git tracking has been enabled for .gitattributes
        • Note: At this state Source Tree will mark any existing files that match the newly created filter as "modified"... so the filter works.
      5. If desired, push the changes back to the remote server.
      6. Add a new file to the repository - the newly created filter should match the file's extension.
        • For example: NewCompressedFile.zip

      Expected Result

      1. You should be able to add the newly created file to a commit, and
      2. when the operation is complete the file should be stored in LFS.

      Actual Result

      • When you try to add the newly created file to a commit, Source Tree will display the following error...

            Assignee:
            Unassigned
            Reporter:
            Pressacco
            Votes:
            8 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: