Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
4.9.1, 4.11.1
-
None
-
None
-
3
-
Severity 2 - Major
-
5
-
Description
Summary
If you push a non-tracked version of a file to Bitbucket Server, then enable lfs and push an lfs-tracked version of the file, the download of the lfs version in a diff returns the pointer file.
Steps to Reproduce
- Commit a binary file to a vanilla git repository.
- Push to a vanilla git Bitbucket Server repository.
- Convert local repository and the Bitbucket Server repository to git-lfs.
- Track the binary file type using git-lfs.
- Commit an update to the binary file.
- Push to Bitbucket Server.
- View the new version in a diff in Bitbucket Server.
Expected Results
The lfs pointer is de-referenced and the new version of the binary is made available to download
Actual Results
Text output showing lfs pointer
Notes
Old version (non-lfs) of the file is available to download
Workaround
None at this time
Attachments
Issue Links
- is duplicated by
-
BSERV-9503 Enabling LFS tracking for an existing image file breaks diff between the pre-LFS and post-LFS commits
- Closed
- mentioned in
-
Page Loading...