Git LFS may not work as expected in a MR across forks

I’ve posted a question today in our Slack:

How do we handle LFS + merge requests (or do we handle it anyhow?)

I mean, let’s say someone added something with git lfs and opened the merge request with that change. Will we copy the blobs from one LFS (theirs) to the other (ours)?

@stanhu:

Good question. I think we don’t need to copy the blob but add the LFS object to the target project. I don’t think we do that.

@brodock: yeah, we also need to keep track of the object so we don’t “garbage collect” when removing the first repository.

GitHub also deals with the problem in a different way (probably removing the blob is not well handled by them, etc). See: https://help.github.com/articles/collaboration-with-git-large-file-storage/