you are viewing a single comment's thread
view the rest of the comments
[–] 6 points 5 days ago* (1 child)

Large files is actually what git-lfs was made for. I haven’t used it extensively but the project has been around for quite a while (implying some measure of stability/userbase). I heard about it over ten years ago.

But your point still stands. GitHub isn’t the solution unless you have few files that you don’t mind being public (because I think GitHub has exposed private repos before).

  • source
  • parent
  • hideshow 1 child comment
  • [–] 8 points 5 days ago

    Yeh, there are workarounds for large & binary files.
    Git-LFS stores a pointer to the file that is stored elsewhere.
    So... you have a git repo of files that point to somewhere that stores the actual files.
    Great if your graphics/assets pipeline or whatever stores the files somewhere, and your codebase uses those assets.
    Not great as the primary system to replace google/microsoft drive.

    Might as well just have/use something that stores the actual files.

  • source
  • parent