Collaboration with Git Large File Storage
With Git LFS enabled, you'll be able to fetch, modify, and push large files just as you would expect with any file that Git manages. However, a user that doesn't have Git LFS will experience a different workflow.
In this article
If collaborators on your repository don't have Git LFS installed, they won't have access to the original large file. If they attempt to clone your repository, they will only fetch the pointer files, and won't have access to any of the actual data.
Tip: To help users without Git LFS enabled, we recommend you set guidelines for repository contributors that describe how to work with large files. For example, you may ask contributors not to modify large files, or to upload changes to a file sharing service like Dropbox or Google Drive. For more information, see "Setting guidelines for repository contributors."
Viewing large files in pull requests
GitHub Enterprise does not render Git LFS objects in pull requests. Only the pointer file is shown:
For more information about pointer files, see "About Git Large File Storage."
To view changes made to large files, check out the pull request locally to review the diff. For more information, see "Checking out pull requests locally."