Set feature flag lfs_auto_link_fork_source to true by default
What does this MR do and why?
This sets the feature flag introduced in !75972 (merged) by default. This has been running in production for over a week (#348243 (closed)).
Previously LFS uploads would always have to be reuploaded to a fork even if the parent already had received the LFS file, but this is unnecessary, wasting time and bandwidth. Consider this sequence of events:
- Push LFS file
test.bin
to project A. - Fork project A to project B.
- Push LFS file
test2.bin
to project A. - Push to project B.
When 4 happens, GitLab should be smart enough to realize that if the user has access to the parent project, then we should be able to link the LFS files in A without requesting a reupload of the file.
Relates to #348243 (closed)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Stan Hu