Handling Sensitive Data (Git LFS)
Discover Git LFS (Large File Storage) for managing large files and preventing sensitive data from being committed directly.
Git & The Big File Problem
Have you ever committed a huge file to Git? Maybe a large image, video, or a big dataset?
Git is designed for text-based code, where changes are small. When you add large binary files, your repository quickly becomes bloated, making cloning and operations slow. This can also happen with sensitive data if not careful.
Why Large Files Bloat Repos
Git stores every version of every file in its history. For text files, Git efficiently stores the differences (deltas).
However, for large binary files (like a 50MB Photoshop file or a compiled executable), even a tiny change means Git stores an entirely new 50MB file. Over time, this makes your repository huge and slow.
All lessons in this course
- Securing Your Git Workflow
- Handling Sensitive Data (Git LFS)
- Best Practices for Commit Messages
- Signing Commits and Tags with GPG