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
Work like you always do on Git—no need for additional commands, secondary storage systems, or toolsets.
The statement is indeed true when using GitHub, Atlassian, GitLab, etc. but if you run your own official git server, it cannot be used as is by git-lfs, so a "secondary storage system" which is a git-lfs server is actually needed. It would be useful to mention this distinction.
Related: Since there is no official git-lfs server implementation yet, one has to dig through implementations to find one which can actually be run and supports the latest git-lfs features. I still did not find any appealing implementation. The page could set better the path/expectations for people with a standard git server.
The text was updated successfully, but these errors were encountered:
it cannot be used as is by git-lfs, so a "secondary storage system" which is a git-lfs server is actually needed. It would be useful to mention this distinction.
Good point! Do you think you could open a PR with some suggested phrasing?
The "Same Git workflow" says:
The statement is indeed true when using GitHub, Atlassian, GitLab, etc. but if you run your own official git server, it cannot be used as is by git-lfs, so a "secondary storage system" which is a git-lfs server is actually needed. It would be useful to mention this distinction.
Related: Since there is no official git-lfs server implementation yet, one has to dig through implementations to find one which can actually be run and supports the latest git-lfs features. I still did not find any appealing implementation. The page could set better the path/expectations for people with a standard git server.
The text was updated successfully, but these errors were encountered: