[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-4913":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":9,"pushedAt":9,"updatedAt":28,"readmeContent":29,"aiSummary":30,"trendingCount":15,"starSnapshotCount":15,"syncStatus":31,"lastSyncTime":32,"discoverSource":33},4913,"git-lfs","git-lfs\u002Fgit-lfs","Git extension for versioning large files","https:\u002F\u002Fgit-lfs.com",null,"Go",14306,2224,467,440,0,1,12,62,6,45,"Other",false,"main",true,[26,5,27],"git","go","2026-06-12 02:01:05","# Git Large File Storage\n\n[![CI status][ci_badge]][ci_url]\n\n[ci_badge]: https:\u002F\u002Fgithub.com\u002Fgit-lfs\u002Fgit-lfs\u002Fworkflows\u002FCI\u002Fbadge.svg\n[ci_url]: https:\u002F\u002Fgithub.com\u002Fgit-lfs\u002Fgit-lfs\u002Factions?query=workflow%3ACI\n\n[Git LFS](https:\u002F\u002Fgit-lfs.github.com) is a command line extension and\n[specification](docs\u002Fspec.md) for managing large files with Git.\n\nThe client is written in Go, with pre-compiled binaries available for Mac,\nWindows, Linux, and FreeBSD. Check out the [website](http:\u002F\u002Fgit-lfs.github.com)\nfor an overview of features.\n\n## Getting Started\n\n### Installing\n\n#### On Linux\n\nDebian and RPM packages are available from packagecloud, see the [Linux installation instructions](INSTALLING.md).\n\n#### On macOS\n\n[Homebrew](https:\u002F\u002Fbrew.sh) bottles are distributed and can be installed via `brew install git-lfs`.\n\n#### On Windows\n\nGit LFS is included in the distribution of [Git for Windows](https:\u002F\u002Fgitforwindows.org\u002F).\nAlternatively, you can install a recent version of Git LFS from the [Chocolatey](https:\u002F\u002Fchocolatey.org\u002F) package manager.\n\n#### Using mise-en-place\n\nIf you are using the [mise-en-place](https:\u002F\u002Fgithub.com\u002Fjdx\u002Fmise) tool manager, Git LFS can be installed and made available in all of your project directories by running:\n\n```ShellSession\n$ mise use --global git-lfs@latest\n```\n\nThe `mise` utility supports Linux, macOS, and Windows, and provides various configuration options including system-wide settings for all users. See the project [documentation](https:\u002F\u002Fmise.jdx.dev) for details on how to use this utility to manage your tools, environment variables, and also some tasks.\n\n#### From binary\n\n[Binary packages](https:\u002F\u002Fgithub.com\u002Fgit-lfs\u002Fgit-lfs\u002Freleases) are\navailable for Linux, macOS, Windows, and FreeBSD.\nThe binary packages include a script which will:\n\n- Install Git LFS binaries onto the system `$PATH`.  On Windows in particular, you may need to restart your command shell so any change to `$PATH` will take effect and Git can locate the Git LFS binary.\n- Run `git lfs install` to perform required global configuration changes.\n\n```ShellSession\n$ .\u002Finstall.sh\n```\n\nNote that Debian and RPM packages are built for multiple Linux distributions and versions for both amd64 and i386.\nFor arm64, only Debian packages are built and only for recent versions due to the cost of building in emulation.\n\n#### From source\n\n- Ensure you have the latest version of Go, GNU make, and a standard Unix-compatible build environment installed.\n- On Windows, install `goversioninfo` with `go install github.com\u002Fjosephspurrier\u002Fgoversioninfo\u002Fcmd\u002Fgoversioninfo@latest`.\n- Run `make`.\n- Place the `git-lfs` binary, which can be found in `bin`, on your system’s executable `$PATH` or equivalent.\n- Git LFS requires global configuration changes once per-machine. This can be done by\nrunning: `git lfs install`\n\n#### Verifying releases\n\nReleases are signed with the OpenPGP key of one of the core team members.  To\nget these keys, you can run the following command, which will print them to\nstandard output:\n\n```ShellSession\n$ curl -L https:\u002F\u002Fapi.github.com\u002Frepos\u002Fgit-lfs\u002Fgit-lfs\u002Ftarball\u002Fcore-gpg-keys | tar -Ozxf -\n```\n\nOnce you have the keys, you can download the `sha256sums.asc` file and verify\nthe file you want like so:\n\n```ShellSession\n$ gpg -d sha256sums.asc | grep git-lfs-linux-amd64-v2.10.0.tar.gz | shasum -a 256 -c\n```\n\nFor the convenience of distributors, we also provide a wider variety of signed\nhashes in the `hashes.asc` file.  Those hashes are in the tagged BSD format, but\ncan be verified with Perl's `shasum` or the GNU hash utilities, just like the\nones in `sha256sums.asc`.\n\n## Example Usage\n\nTo begin using Git LFS within a Git repository that is not already configured\nfor Git LFS, you can indicate which files you would like Git LFS to manage.\nThis can be done by running the following _from within a Git repository_:\n\n```bash\n$ git lfs track \"*.psd\"\n```\n\n(Where `*.psd` is the pattern of filenames that you wish to track. You can read\nmore about this pattern syntax\n[here](https:\u002F\u002Fgit-scm.com\u002Fdocs\u002Fgitattributes)).\n\n> *Note:* the quotation marks surrounding the pattern are important to\n> prevent the glob pattern from being expanded by the shell.\n\nAfter any invocation of `git-lfs-track(1)` or `git-lfs-untrack(1)`, you _must\ncommit changes to your `.gitattributes` file_. This can be done by running:\n\n```bash\n$ git add .gitattributes\n$ git commit -m \"track *.psd files using Git LFS\"\n```\n\nYou can now interact with your Git repository as usual, and Git LFS will take\ncare of managing your large files. For example, changing a file named `my.psd`\n(tracked above via `*.psd`):\n\n```bash\n$ git add my.psd\n$ git commit -m \"add psd\"\n```\n\n> _Tip:_ if you have large files already in your repository's history, `git lfs\n> track` will _not_ track them retroactively. To migrate existing large files\n> in your history to use Git LFS, use `git lfs migrate`. For example:\n>\n> ```\n> $ git lfs migrate import --include=\"*.psd\" --everything\n> ```\n>\n> **Note that this will rewrite history and change all of the Git object IDs in your\n> repository, just like the export version of this command.**\n>\n> For more information, read [`git-lfs-migrate(1)`](https:\u002F\u002Fgithub.com\u002Fgit-lfs\u002Fgit-lfs\u002Fblob\u002Fmain\u002Fdocs\u002Fman\u002Fgit-lfs-migrate.adoc).\n\nYou can confirm that Git LFS is managing your PSD file:\n\n```bash\n$ git lfs ls-files\n3c2f7aedfb * my.psd\n```\n\nOnce you've made your commits, push your files to the Git remote:\n\n```bash\n$ git push origin main\nUploading LFS objects: 100% (1\u002F1), 810 B, 1.2 KB\u002Fs\n# ...\nTo https:\u002F\u002Fgithub.com\u002Fgit-lfs\u002Fgit-lfs-test\n   67fcf6a..47b2002  main -> main\n```\n\n### Uninstalling\n\nIf you've decided that Git LFS isn't right for you, you can convert your\nrepository back to a plain Git repository with `git lfs migrate` as well.  For\nexample:\n\n```ShellSession\n$ git lfs migrate export --include=\"*.psd\" --everything\n```\n\n**Note that this will rewrite history and change all of the Git object IDs in your\nrepository, just like the import version of this command.**\n\nIf there's some reason that things aren't working out for you, please let us\nknow in an issue, and we'll definitely try to help or get it fixed.\n\n## Limitations\n\nGit LFS maintains a list of currently known limitations, which you can find and\nedit [here](https:\u002F\u002Fgithub.com\u002Fgit-lfs\u002Fgit-lfs\u002Fwiki\u002FLimitations).\n\nCurrent releases of Git LFS will work with Git versions as early as\nGit 2.0.0.  However, for best performance, using a recent version of Git\nis highly recommended.\n\nGit LFS source code utilizes Go modules in its build system, and therefore this\nproject contains a `go.mod` file with a defined Go module path.  However, we\ndo not maintain a stable Go language API or ABI, as Git LFS is intended to be\nused solely as a compiled binary utility.  Please do not import the `git-lfs`\nmodule into other Go code and do not rely on it as a source code dependency.\n\n## Need Help?\n\nYou can get help on specific commands directly:\n\n```bash\n$ git lfs help \u003Csubcommand>\n```\n\nThe [official documentation](docs) has command references and specifications for\nthe tool.  There's also a [FAQ](https:\u002F\u002Fgithub.com\u002Fgit-lfs\u002Fgit-lfs\u002Fblob\u002Fmain\u002Fdocs\u002Fman\u002Fgit-lfs-faq.adoc)\nshipped with Git LFS which answers some common questions.\n\nIf you have a question on how to use Git LFS, aren't sure about something, or\nare looking for input from others on tips about best practices or use cases,\nfeel free to\n[start a discussion](https:\u002F\u002Fgithub.com\u002Fgit-lfs\u002Fgit-lfs\u002Fdiscussions).\n\nYou can always [open an issue](https:\u002F\u002Fgithub.com\u002Fgit-lfs\u002Fgit-lfs\u002Fissues), and\none of the Core Team members will respond to you. Please be sure to include:\n\n1. The output of `git lfs env`, which displays helpful information about your\n   Git repository useful in debugging.\n2. Any failed commands re-run with `GIT_TRACE=1` in the environment, which\n   displays additional information pertaining to why a command crashed.\n\n## Contributing\n\nSee [CONTRIBUTING.md](CONTRIBUTING.md) for info on working on Git LFS and\nsending patches. Related projects are listed on the [Implementations wiki\npage](https:\u002F\u002Fgithub.com\u002Fgit-lfs\u002Fgit-lfs\u002Fwiki\u002FImplementations).\n\nSee also [SECURITY.md](SECURITY.md) for info on how to submit reports\nof security vulnerabilities.\n\n## Core Team\n\nThese are the humans that form the Git LFS core team, which runs the project.\n\nIn alphabetical order:\n\n| [@chrisd8088][chrisd8088-user] | [@larsxschneider][larsxschneider-user] |\n| :---: | :---: |\n| [![][chrisd8088-img]][chrisd8088-user] | [![][larsxschneider-img]][larsxschneider-user] |\n| [PGP 088335A9][chrisd8088-pgp] | [PGP A5795889][larsxschneider-pgp] |\n\n[chrisd8088-img]: https:\u002F\u002Favatars1.githubusercontent.com\u002Fu\u002F28857117?s=100&v=4\n[larsxschneider-img]: https:\u002F\u002Favatars1.githubusercontent.com\u002Fu\u002F477434?s=100&v=4\n[chrisd8088-user]: https:\u002F\u002Fgithub.com\u002Fchrisd8088\n[larsxschneider-user]: https:\u002F\u002Fgithub.com\u002Flarsxschneider\n[chrisd8088-pgp]: https:\u002F\u002Fkeyserver.ubuntu.com\u002Fpks\u002Flookup?op=get&search=0x86cd3297749375bcf8206715f54fe648088335a9\n[larsxschneider-pgp]: https:\u002F\u002Fkeyserver.ubuntu.com\u002Fpks\u002Flookup?op=get&search=0xaa3b3450295830d2de6db90caba67be5a5795889\n\n### Alumni\n\nThese are the humans that have in the past formed the Git LFS core team, or\nhave otherwise contributed a significant amount to the project. Git LFS would\nnot be possible without them.\n\nIn alphabetical order:\n\n| [@andyneff][andyneff-user] | [@bk2204][bk2204-user] | [@PastelMobileSuit][PastelMobileSuit-user] | [@rubyist][rubyist-user] | [@sinbad][sinbad-user] | [@technoweenie][technoweenie-user] | [@ttaylorr][ttaylorr-user] |\n| :---: | :---: | :---: | :---: | :---: | :---: | :---: |\n| [![][andyneff-img]][andyneff-user] | [![][bk2204-img]][bk2204-user] | [![][PastelMobileSuit-img]][PastelMobileSuit-user] | [![][rubyist-img]][rubyist-user] | [![][sinbad-img]][sinbad-user] | [![][technoweenie-img]][technoweenie-user] | [![][ttaylorr-img]][ttaylorr-user] |\n\n[andyneff-img]: https:\u002F\u002Favatars1.githubusercontent.com\u002Fu\u002F7596961?v=3&s=100\n[bk2204-img]: https:\u002F\u002Favatars1.githubusercontent.com\u002Fu\u002F497054?s=100&v=4\n[PastelMobileSuit-img]: https:\u002F\u002Favatars2.githubusercontent.com\u002Fu\u002F37254014?s=100&v=4\n[rubyist-img]: https:\u002F\u002Favatars1.githubusercontent.com\u002Fu\u002F143?v=3&s=100\n[sinbad-img]: https:\u002F\u002Favatars1.githubusercontent.com\u002Fu\u002F142735?v=3&s=100\n[technoweenie-img]: https:\u002F\u002Favatars3.githubusercontent.com\u002Fu\u002F21?v=3&s=100\n[ttaylorr-img]: https:\u002F\u002Favatars2.githubusercontent.com\u002Fu\u002F443245?s=100&v=4\n[andyneff-user]: https:\u002F\u002Fgithub.com\u002Fandyneff\n[bk2204-user]: https:\u002F\u002Fgithub.com\u002Fbk2204\n[PastelMobileSuit-user]: https:\u002F\u002Fgithub.com\u002FPastelMobileSuit\n[sinbad-user]: https:\u002F\u002Fgithub.com\u002Fsinbad\n[rubyist-user]: https:\u002F\u002Fgithub.com\u002Frubyist\n[technoweenie-user]: https:\u002F\u002Fgithub.com\u002Ftechnoweenie\n[ttaylorr-user]: https:\u002F\u002Fgithub.com\u002Fttaylorr\n","Git LFS 是一个用于管理 Git 中大文件版本的命令行扩展和规范。该项目使用 Go 语言编写，支持 Mac、Windows、Linux 和 FreeBSD 等平台，并提供了预编译的二进制文件。其核心功能包括高效地处理大型文件（如音频、视频等），通过将这些文件存储在远程服务器上而只在本地保留指针，从而大大减少了仓库的大小。这种机制非常适合需要频繁更新大文件但又希望保持代码库轻量级的开发场景，比如游戏开发、多媒体项目等。此外，Git LFS 易于安装且与标准 Git 工具兼容良好，使得它可以无缝集成到现有的工作流中。",2,"2026-06-11 03:01:28","top_language"]