https://DevOpsCloud.io -- Cloud Monk Losang Jinpa, Ph.D., MCSE/MCT, GitOps DevOps Engineer

Git Large File Storage (LFS)

GitHub related ONLY: Give me a 500 term vocabulary list sorted by popularity in usage (by commonly used / frequency of use in codebases). That means 500 terms, not 500 words. DO NOT REPEAT YOURSELF. Acronyms related to GitHub technology are allowed but they must be expanded. e.g. RAII (Resource Acquisition Is Initialization). The terms should have to do ONLY with and SPECIFICALLY with GitHub, CANNOT include generic operating system terms, generic IT terms, or computing terms. No definitions. Just the words. Each word should be surrounded by double brackets and separated by a comma and on the same lines. e.g. robots, robotics. Etc.

GitHub, repository, fork, pull request, merge request, branch, main branch, default branch, commit, merge, conflict resolution, issue, issue tracker, milestone, labels, assignees, contributors, collaborators, workflow, actions, GitHub Actions, runner, workflow file, YAML, CI/CD (Continuous Integration/Continuous Deployment), repository secrets, environment variables, webhook, API (Application Programming Interface), REST API, GraphQL API, OAuth authentication, personal access token, SSH key, GPG key, GitHub Pages, static site generator, Markdown, README.md, CONTRIBUTING.md, LICENSE, codeowners, GitHub Classroom, GitHub Sponsors, GitHub Enterprise, GitHub Enterprise Server, GitHub Enterprise Cloud, GitHub Actions Marketplace, GitHub Marketplace, dependabot, code scanning, vulnerability alerts, dependency graph, GitHub Packages, GitHub Container Registry, Dockerfile, Docker image, actions/cache, actions/upload-artifact, actions/download-artifact, actions/checkout, GitHub Runner, self-hosted runner, GitHub CLI (Command Line Interface), gh CLI, gh workflow, gh repo, gh issue, gh pr, gh release, GitHub Insights, GitHub Metrics, commit graph, contribution heatmap, activity log, GitHub Wiki, GitHub Discussions, GitHub Codespaces, VSCode integration, dev container, GitHub Copilot, Copilot Labs, Copilot CLI, AI pair programming, GitHub Education, GitHub Campus Experts, GitHub Student Developer Pack, GitHub Security Lab, Secret Scanning, GitHub Dependabot Alerts, SAML single sign-on, SSO (Single Sign-On), GitHub Audit Logs, repo sync, GitHub Importer, migrate repositories, collaboration tools, project board, Kanban board, GitHub Projects, GitHub Team Discussions, GitHub Organization, organization-level permissions, team management, team discussions, team sync, GitHub Archive, GitHub Archive Program, Arctic Code Vault, repo insights, GitHub RESTful API, GitHub GraphQL API Explorer, GitHub Webhooks, GitHub Actions Runner, GitHub Secrets, GitHub Artifact Storage, GitHub Custom Actions, custom GitHub Actions, GitHub-hosted runners, Linux runner, Windows runner, macOS runner, GitHub Actions Cache, GitHub Artifact Cache, action.yml, GitHub Action Metadata, GitHub Flavored Markdown, GFM (GitHub Flavored Markdown), emoji in Markdown, Markdown linting, pre-commit hook, commit message guidelines, squash merge, rebase and merge, merge commit, protection rules, branch protection, branch restrictions, branch policies, code review, pull request reviews, PR approvals, required reviewers, draft pull request, pull request template, issue template, GitHub Insights Dashboard, team analytics, repository analytics, GitHub Action Logs, Actions tab, Jobs tab, GitHub Actions API, workflow logs, workflow run, actions workflow, GitHub Organization-level Actions, custom action development, Docker action, JavaScript action, GitHub Workflow Commands, GitHub Logs, repo settings, repo secrets, environment secrets, GitHub Profile README, personal README, pinned repositories, GitHub Sponsor button, community profile, community standards, project automation, project automation rules, automation tasks, dependabot config, security advisories, GitHub CVE Alerts, CVE identifiers, dependency vulnerabilities, code scanning alerts, SARIF (Static Analysis Results Interchange Format), custom query packs, GitHub CodeQL, CodeQL Analysis, GitHub DevOps, GitHub CI integration, CI badges, workflow badges, GitHub Pages Custom Domain, CNAME setup, HTTPS enforcement, DNS configuration, GitHub Actions Manual Trigger, workflow_dispatch, schedule trigger, cron job in Actions, GitHub Deployment, GitHub Deployments API, GitHub Releases, release drafts, release assets, pre-release, GitHub Actions Runner Groups, runner group settings, GitHub Advanced Security, security policies, security workflows, GitHub Organization Webhooks, webhook events, repository dispatch, GitHub Events API, starred repositories, GitHub Stars, starring a repo, watching a repository, fork syncing, fork update, branch comparison, compare view, diff view, unified diff, split diff, pull request checks, required status checks, continuous testing, GitHub Test Matrix, matrix builds, matrix workflows, GitHub Run ID, job outputs, GitHub Actions Artifact Upload, artifacts download, GitHub Hosted Runners, runner versions, GitHub Dependabot PR, automated dependency updates, GitHub Auto-merge, pull request automation, review request automation, GitHub Notification Settings, repo notifications, team notifications, organization notifications, GitHub Blame View, line history, file history, commit history, repo tags, GitHub Milestones, milestone tracking, GitHub Discussions Tab, threaded discussions, locked conversations, resolved conversations, GitHub Contribution Graph, activity overview, commit frequency, contribution insights, GitHub Copilot Chat, Copilot suggestions, PR linting, GitHub Action Timeout, job timeout, action retries, GitHub Pages Workflow, pages build, GitHub Actions Deployment.

GitHub: GitOps, GitHub Copilot (Learn AI-Assisted Python Programming), GitHub for Major Software and Languages, GitHub Fundamentals, GitHub Inventor: GitHub and Git, GitHub Stars: GitHub Organization Ranking, GitHub Stars Ranking, GitHub Star Ranking for Repositories, GitHub Big Tech, Cloud Monk's favorite GitHub repos, gh plugin, git help, Version control, GitHub topics, Git topics, Git, GitHub repos, GitHub bibliography, Manning Git-GitHub Series, GitHub Actions, GitHub CodeSpaces, GitHub CLI, GitHub Free, GitHub Pro, GitHub Team, GitHub Enterprise, GitHub security (GitHub MFA –> GitHub Two-Factor Methods - GitHub Passkeys) - GitHub Secrets - Authenticating with GitHub from Git (gh auth login), GLFS, GitHub Packages, GitHub alternative source code repos (GitHub - GitLab - AWS CodeCommit - Google Cloud Source Repositories - Bitbucket), Install Git, Git for Windows (choco search github, brew search github), Git for Linux, Git for macOS, GitHub Glossary - Glossaire de GitHub - French, Git Glossary - Glossaire de Git - French. (navbar_github - see also navbar_git, navbar_gitops, navbar_gitlab, navbar_azure_devops, navbar_iac)

Large File Storage - https://git-lfs.github.com

“Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.”

Features

“Large file versioning: Version large files – even those as large as a couple GB in size with Git.
More repository space: Host more in your Git repositories. External file storage makes it easy to keep your repository at a manageable size.
Faster cloning and fetching: Download less data. This means faster cloning and fetching from repositories that deal with large files.
Same Git workflow: Work like you always do on Git-no need for additional commands, secondary storage systems, or toolsets.
Same access controls and permissions: Keep the same access controls and permissions for large files as the rest of your Git repository when working with a remote host like GitHub.”

Git Large File Storage (LFS), Git LFS, Git Large File Storage, Large File Storage (LFS)

Fair Use Source:

https://community.chocolatey.org/packages/git-lfs

“GitHub limits the size of files allowed in repositories. To track files beyond this limit, you can use Git Large File Storage.”

About Git Large File Storage

“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 which 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.”

Using Git LFS, you can store files up to:

Product Maximum file size

Fair Use Source: https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-git-large-file-storage

https://www.atlassian.com/git/tutorials/git-lfs

Installation

Windows

Via Chocolatey - https://community.chocolatey.org/packages/git-lfs

choco install git-lfs -y

Chocolatey v0.11.2

Installing the following packages:

git-lfs

By installing, you accept licenses for the packages.

Progress: Downloading git-lfs.install 3.0.1… 100%

Progress: Downloading git-lfs 3.0.1… 100%

git-lfs.install v3.0.1 [Approved]

git-lfs.install package files install completed. Performing other installation steps.

Installing git-lfs…

git-lfs has been installed.

git-lfs.install can be automatically uninstalled.

Environment Vars (like PATH) have changed. Close/reopen your shell to see the changes (or in PowerShell / cmd.exe just type `refreshenv`).

The install of git-lfs.install was successful.

Software installed to '\Program Files\Git LFS\'

git-lfs v3.0.1 [Approved]

git-lfs package files install completed. Performing other installation steps.

The install of git-lfs was successful.

Software install location not explicitly set, it could be in package or default install location of installer.

Chocolatey installed 2/2 packages.

See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).

Getting Started

Download and install the Git command line extension. Once downloaded and installed, set up Git LFS for your user account by running:

git lfs install

Git LFS initialized.

You only need to run this once per user account.

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 anytime.

git lfs track “

.psd”

Now make sure .gitattributes is tracked:

git add .gitattributes

Note that defining the file types Git LFS should track will not, by itself, convert any pre-existing files to Git LFS, such as files on other branches or in your prior commit history. To do that, use the git lfs migrate[1] command, which has a range of options designed to suit various potential use cases.

There is no step three. Just commit and push to GitHub as you normally would; for instance, if your current branch is named main:

git add file.psd

git commit -m “Add design file”

git push origin main

Check out our wiki, discussion forum, and documentation for help with any questions you might have!