Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
-
2
-
Description
Because git-lfs on the client relies on a pre-push hook to actually upload LFS files, it is possible for a user to complete a push without uploading any LFS files.
This may happen if a user is working from a new clone or worktree and has the LFS filters installed in their global .gitconfig but does not have the LFS hook properly installed in their repo's .git/hooks directory.
Because LFS files are uploaded from a pre-push hook, Bitbucket Server should be able to detect when a push contains LFS pointers to files that weren't already pushed to or otherwise don't exist in LFS storage. In this case, the offending push should be rejected.
Currently, if this were to happen the error wouldn't be caught until much later, and it would be caught by our build server instead of by the user or by Bitbucket Server.