-
Suggestion
-
Resolution: Unresolved
Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server.
With Git LFS 2.0.0 you can now lock files that you're actively working on, preventing others from pushing to the Git LFS server until you unlock the files again.
This will prevent merge conflicts as well as lost work on non-mergeable files at the filesystem level. While it may seem to contradict the distributed and parallel nature of Git, file locking is an important part of many software development workflows particularly for larger teams working with binary assets.
https://github.com/blog/2328-git-lfs-2-0-0-released\\
https://github.com/git-lfs/git-lfs/wiki/File-Locking
What I'm thinking is not only a visual representation on your website GUI but also some front-end functionality on SourceTree such as the currently implemented SourceTree Git LFS warning that XYZ file(S) are larger than 2MB.
I'd look to GitLab's iteration for guidance: https://docs.gitlab.com/ee/user/project/file_lock.html
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BCLOUD-14454] Git LFS (v2.x) File Locking Support
This feature is crucial for our team. Please consider adding it
Hi there! This would be of great help with Unreal Engine based projects! Please consider it.
any news?
migrated to Bitbucket Cloud and it is being surprise after surprise... I´m very unhappy with the Bitbucket Cloud product.
Is there any roadmap or estimate of when we will be able to offer our users LFS Locking?
This feature is absolutely essential for what we do.
Why is it taking so long to implement?
OUR STORAGE SPACE IS LIMITED AMOUNT IN BUICK PROJRECT1 mail@example.com
This issue has gathered enough interest to be moved automatically to Reviewing status, where it will be reviewed to someone in the relevant product development team and moved on to the appropriate status.