You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,6 +59,10 @@ or from the same page:
59
59
60
60
> Store programmatically generated files outside of Git, such as in object storage.
61
61
62
+
[`DVC`](https://github.com/iterative/dvc):
63
+
64
+
> Store them in your cloud storage but keep their version info in your Git repo.
65
+
62
66
## Why not Git LFS as the primary model
63
67
64
68
Git LFS is better than checking large blobs directly into normal Git history, but it is still not the model we want to optimize around here.
@@ -74,10 +78,6 @@ The strongest reasons are:
74
78
75
79
> So adoption of Git LFS is a one way door that can't be easily reversed.
76
80
77
-
[`DVC`](https://github.com/iterative/dvc):
78
-
79
-
> Store them in your cloud storage but keep their version info in your Git repo.
80
-
81
81
Operational failure modes are documented very explicitly:
82
82
83
83
from [GitHub LFS billing and quota behavior](https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage):
0 commit comments