• Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      An open source Git extension for versioning large files

      Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.

      Features

      By design, every git repository contains every version of every file. But for some types of projects, this is not reasonable or even practical. Multiple revisions of a large file take up space quickly, slowing down repository operations and making fetches unwieldy.

      Git LFS overcomes this limitation by storing the metadata for large files in Git and syncing the file contents to a configurable Git LFS server. Some of the key features include:

      • Tight integration with Git means you don't have to change your workflow after the initial configuration.
      • Large files are synced separately to a configurable Git LFS server over HTTPS, so you are not limited in where you push your Git repository.
      • Large files are only synced from the server when they are checked out, so your local repository doesn't carry the weight of every version of every file when it is not needed.
      • The meta data stored in Git is extensible for future use. It currently includes a hash of the contents of the file, and the file size so clients can display a progress bar while downloading or opt out of a large download.
      • Clients and servers can make use of all the features of HTTPS, such as caching content locally on a CDN, resumable uploads and downloads, or performing requests in parallel for faster transfers.

      More Info: https://git-lfs.github.com/
      Source Code: https://github.com/github/git-lfs

          Form Name

            [BSERV-7300] Support Git Large File Storage (LFS) extension

            steve added a comment -

            Hi everyone,

            My apologies that I didn't get on this thread a couple of days ago. Currently, this issue is closed as it is a duplicate of STASH-4027 - I have recently updated the original ticket with information about our progress on this feature request. I'd encourage you to watch and vote on the issue there and see the update in the description.

            Thanks again,
            Steve.

            steve added a comment - Hi everyone, My apologies that I didn't get on this thread a couple of days ago. Currently, this issue is closed as it is a duplicate of STASH-4027 - I have recently updated the original ticket with information about our progress on this feature request. I'd encourage you to watch and vote on the issue there and see the update in the description. Thanks again, Steve.

            Awesome news joerg.herzinger & thank you for taking up the challenge

            I'll take a better look at your codebase later this week, though just an FYI that my field is more design/art over that of programming but I'll see if I can help out nonetheless, as I'm pretty familiar with Git command prompt which might help

            Benjamin D. Smith added a comment - Awesome news joerg.herzinger & thank you for taking up the challenge I'll take a better look at your codebase later this week, though just an FYI that my field is more design/art over that of programming but I'll see if I can help out nonetheless, as I'm pretty familiar with Git command prompt which might help

            I've started some work on this topic. There is still a lot to do, but basically it is already fully working: https://github.com/joerg/stash-git-lfs
            Any help is appreciated. Just send me a pull request, write an email or file a bug.

            Jörg Herzinger added a comment - I've started some work on this topic. There is still a lot to do, but basically it is already fully working: https://github.com/joerg/stash-git-lfs Any help is appreciated. Just send me a pull request, write an email or file a bug.

            Benjamin D. Smith added a comment - - edited

            rbarnes it is a matter of what the competition is doing & signs that you should probably follow or risk being left in the dust...

            Nonetheless,
            I do get what you're saying regarding production workflows for feature implantation a

            Benjamin D. Smith added a comment - - edited rbarnes it is a matter of what the competition is doing & signs that you should probably follow or risk being left in the dust... Nonetheless, I do get what you're saying regarding production workflows for feature implantation a

            Thanks Ben! If only we implemented features based on the number of places it had been mentioned. This would totally win

            Roger Barnes (Inactive) added a comment - Thanks Ben! If only we implemented features based on the number of places it had been mentioned. This would totally win

            I should also mention that you can find the BitBucket counterpart for this request here: https://bitbucket.org/site/master/issue/11204/support-git-lfs-extension

            Benjamin D. Smith added a comment - I should also mention that you can find the BitBucket counterpart for this request here: https://bitbucket.org/site/master/issue/11204/support-git-lfs-extension

            Hi rbarnes,
            We are currently using default Git behaviour with the only addition being Git Flow. Our workflow primarily consists of making a seperate branch for any binary files which will most likely have a lot of activity commits wise before squishing than merging back into our develop branch, at which point we delete the branch containing the many binary file revision commits.

            We also make heavy use of both Git Submodules for source assets like .PSD files, etc as they do not directly interact with our primary repositories like the exported JPEG, PNG, etc files do.

            With that being said,
            We are interesting in Perforce Fusion + Helix & while we also make small use of SVN<->GIT configurations for some of our much larger binary file sets we would prefer to have a 1-solution fits all system for our source control needs & Stash isn't really cutting it in that regards currently...

            Furthermore,
            I think that this issue should be marked as related & not a duplicate of STASH-4027, as Git LFS is well on its way to becoming an industry standard within the Git world & such companies as GitHub are looking to support it by default.

            GitHub Git LFS News Source: https://github.com/blog/1986-announcing-git-large-file-storage-lfs

            Benjamin D. Smith added a comment - Hi rbarnes , We are currently using default Git behaviour with the only addition being Git Flow. Our workflow primarily consists of making a seperate branch for any binary files which will most likely have a lot of activity commits wise before squishing than merging back into our develop branch, at which point we delete the branch containing the many binary file revision commits. We also make heavy use of both Git Submodules for source assets like .PSD files, etc as they do not directly interact with our primary repositories like the exported JPEG, PNG, etc files do. With that being said, We are interesting in Perforce Fusion + Helix & while we also make small use of SVN<->GIT configurations for some of our much larger binary file sets we would prefer to have a 1-solution fits all system for our source control needs & Stash isn't really cutting it in that regards currently... Furthermore, I think that this issue should be marked as related & not a duplicate of STASH-4027 , as Git LFS is well on its way to becoming an industry standard within the Git world & such companies as GitHub are looking to support it by default. GitHub Git LFS News Source: https://github.com/blog/1986-announcing-git-large-file-storage-lfs

            Hi Benjamin, thanks for the suggestion. Would love to hear more about how you're working with large files currently. Since this is close to another ticket you've participated in already, I'd like to suggest we keep the discussion on STASH-4027 . I've added a mention of git-lfs there as another example of large file extensions git could work with.

            Roger Barnes (Inactive) added a comment - Hi Benjamin, thanks for the suggestion. Would love to hear more about how you're working with large files currently. Since this is close to another ticket you've participated in already, I'd like to suggest we keep the discussion on STASH-4027 . I've added a mention of git-lfs there as another example of large file extensions git could work with.

            I've created an issue on the Git LFS GitHub repository to spread awareness on this topic: https://github.com/github/git-lfs/issues/249

            Benjamin D. Smith added a comment - I've created an issue on the Git LFS GitHub repository to spread awareness on this topic: https://github.com/github/git-lfs/issues/249

              Unassigned Unassigned
              1875d5160769 Benjamin D. Smith
              Votes:
              0 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: