Approach 1 Using Git LFS

Github has file size limits of 100MB. Files with a size of 50MB trigger a warning message but can still be pushed through.

Git Large File Storage (LFS) is an open-source Git extension that allows users to store large files and binary files separately in the main Git repository. Instead of storing actual files or Binary Large Objects (blobs) in the Git repository itself, Git LFS replaces them with text pointers. The actual file contents are stored on a remote server, such as GitHub.com or GitHub Enterprise. This allows users to work with large files in a Git repository without bloating the repository size.

Example:

If there are existing large files in your repository that resist Git further from accepting your changes and you would like to keep them in GitHub. In that scenario, you need to first remove those files from the repository and then add them to Git LFS locally. Let us see those steps in detail.

Step 1: Install Git LFS on your system.

(i) Download Git LFS.
(ii) Locate the downloaded file and install Git-LFS on your system.

(iii) Verify that the installation was successful:

C:\Windows\System32>git lfs install
Git LFS initialized.

Step 2: Configure Git Large File Storage.

(i) Open Git Bash.
(ii) Set the directory path to an existing repository path, where you want to use Git LFS.
(iii) Select the file types you would like Git LFS to manage, You can configure additional file extensions at any time by using the following command:

git lfs track 

For example, to associate a .psd file, enter the following command:

git lfs track "*.psd"                

Here I want to track a .glb file. Let’s try to configure it.

Step 3:

(i) Commit your local .gitattributes file into your repository.
(ii) Add a file to the repository matching the extension you’ve associated:
(iii) Commit and push your changes into remote.

Now, we will add a .glb file and with this .gitattributes file into our repo.

git add path/to/file.glb
git   add  .gitattributes

Changes we make in the remote repository.

We Didn’t get much of what was happening, only added the local files to the remote server.

Git LFS handles large files by storing references to the file in the repository, but not the actual file itself. To work around Git’s architecture, Git LFS creates a pointer file that acts as a reference to the actual file (which is stored somewhere else). GitHub manages this pointer file in your repository. When you clone the repository down, GitHub uses the pointer file as a map to go and find the large file for you.

One important point is to remember, to commit your local .gitattributes file into your repository.

Relying on a global .gitattributes file associated with Git LFS may cause conflicts when contributing to other Git projects.

In each Git repository where you want to use Git LFS, select the file types you’d like Git LFS to manage (or directly edit your .gitattributes). You can configure additional file extensions at any time.

Version Control Systems are a category of software tools that help in recording changes made to files by keeping track of modifications done in the code.

Purpose of Version Control System:

• Multiple people can work simultaneously on a single project. Everyone works on and edits their copy of the files and it is up to them when they wish to share the changes made by them with the rest of the team.
• Version control provides access to the historical versions of a project. This is insurance against computer crashes or data loss. If any mistake is made, you can easily roll back to a previous version. It is also possible to undo specific edits that too without losing the work done in the meantime. It can be easily known when, why, and by whom any part of a file was edited.

Git is a free and open-source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. When you do actions in Git, nearly all of them only add data to the Git database.