Why Git LFS for large files? - Purpose & Use Cases

The Big Idea

What if your huge project files could stay fast and light without losing any data?

The Scenario

Imagine you are working on a project with huge images or videos. You try to save them directly in your Git repository like normal files.

The Problem

Saving big files directly makes your repository very slow and heavy. Every time you clone or pull, it takes a long time and uses lots of space. Mistakes happen when files get corrupted or versions get mixed up.

The Solution

Git LFS stores only small pointers in your repository and keeps the big files separately. This keeps your project fast and clean while still tracking large files easily.

Before vs After

✗ Before

git add big_video.mp4
git commit -m "Add big video"

✓ After

git lfs track "*.mp4"
git add .gitattributes big_video.mp4
git commit -m "Add big video with LFS"

What It Enables

You can work with large files smoothly without slowing down your whole project or wasting space.

Real Life Example

A game developer stores huge textures and sound files using Git LFS, so the team can share updates quickly without waiting hours for downloads.

Key Takeaways

Large files slow down normal Git repositories.

Git LFS keeps big files outside the main repo, using pointers instead.

This makes working with big files fast and easy.

Practice

1. What is the main purpose of Git LFS (Large File Storage)?

easy

A. To convert large files into text files for easier diffing

B. To speed up Git commit operations by compressing files

C. To automatically merge large files during conflicts

D. To store large files outside the main Git repository history

Solution

1. Step 1: Understand Git LFS functionality

   Git LFS stores large files outside the main Git history to keep the repository lightweight.

2. Step 2: Compare options with Git LFS purpose

   Options A, B, and C describe unrelated features; only To store large files outside the main Git repository history matches Git LFS's main goal.

3. Final Answer:

   To store large files outside the main Git repository history -> Option D

4. Quick Check:

   Git LFS purpose = store large files externally [OK]

Hint: Git LFS stores big files outside Git history [OK]

Common Mistakes:

• Thinking Git LFS compresses files inside Git
• Assuming Git LFS merges conflicts automatically
• Believing Git LFS converts files to text

2. Which command correctly tracks all .psd files using Git LFS?

easy

A. git track lfs *.psd

B. git lfs track "*.psd"

C. git lfs add *.psd

D. git add lfs *.psd

Solution

1. Step 1: Recall Git LFS tracking syntax

   The correct command to track files is git lfs track "pattern".

2. Step 2: Check each option's syntax

   Only git lfs track "*.psd" uses the correct command and pattern syntax. Others are invalid commands.

3. Final Answer:

   git lfs track "*.psd" -> Option B

4. Quick Check:

   Correct Git LFS track syntax = git lfs track [OK]

Hint: Use 'git lfs track "*.ext"' to track file types [OK]

Common Mistakes:

• Swapping command order like 'git track lfs'
• Using 'git lfs add' instead of 'track'
• Trying to add files directly with 'git add lfs'

3. After running git lfs track "*.mp4" and committing, what will happen when you add a new video.mp4 file and push?

medium

A. The video.mp4 file is stored in Git LFS and pushed separately

B. The video.mp4 file is pushed as a normal Git blob

C. Git will reject the push because video.mp4 is too large

D. The video.mp4 file is ignored and not pushed

Solution

1. Step 1: Understand effect of tracking and committing .gitattributes

   Tracking '*.mp4' and committing .gitattributes tells Git to use LFS for .mp4 files.

2. Step 2: Add and push a new .mp4 file

   Git LFS stores the file outside Git history and pushes it separately, so The video.mp4 file is stored in Git LFS and pushed separately is correct.

3. Final Answer:

   The video.mp4 file is stored in Git LFS and pushed separately -> Option A

4. Quick Check:

   Tracked files use LFS storage on push [OK]

Hint: Tracked files go to LFS storage on push [OK]

Common Mistakes:

• Assuming large files push normally without LFS
• Thinking Git rejects large files automatically
• Believing tracked files are ignored

4. You ran git lfs track "*.zip" but forgot to commit .gitattributes. What problem will occur?

medium

A. Git LFS will track .zip files but not push them

B. Git will refuse to add .zip files locally

C. Git LFS will not track .zip files on other clones

D. No problem; tracking works without committing .gitattributes

Solution

1. Step 1: Understand role of .gitattributes in Git LFS

   .gitattributes stores tracking rules and must be committed to share them.

2. Step 2: Effect of not committing .gitattributes

   Other clones won't know to track .zip files with LFS, so Git LFS will not track .zip files on other clones is correct.

3. Final Answer:

   Git LFS will not track .zip files on other clones -> Option C

4. Quick Check:

   Commit .gitattributes to share LFS tracking [OK]

Hint: Always commit .gitattributes after tracking files [OK]

Common Mistakes:

• Assuming local tracking affects other clones
• Thinking Git blocks adding files without .gitattributes
• Believing tracking works without committing

5. You want to track both .psd and .mp4 files with Git LFS. Which sequence correctly sets this up and shares it with your team?

hard

A. Run git lfs track "*.psd" and git lfs track "*.mp4", then commit and push .gitattributes

B. Run git lfs track "*.psd *.mp4" and push without committing

C. Add files with git add *.psd *.mp4 then run git lfs install

D. Run git lfs track "*.psd" only, then manually add .mp4 files

Solution

1. Step 1: Track each file type separately

   Git LFS requires separate track commands for each pattern, so run both track commands.

2. Step 2: Commit and push .gitattributes to share tracking

   Committing and pushing .gitattributes shares tracking rules with the team.

3. Final Answer:

   Run git lfs track "*.psd" and git lfs track "*.mp4", then commit and push .gitattributes -> Option A

4. Quick Check:

   Track each pattern + commit .gitattributes [OK]

Hint: Track each pattern separately and commit .gitattributes [OK]

Common Mistakes:

• Trying to track multiple patterns in one command incorrectly
• Forgetting to commit .gitattributes
• Running git lfs install after adding files