be411309fd
In [1] and [2], callers of the 'git lfs migrate' command were surprised when `--everything` did not migrate over everything, as its name implies. In the documentation, we specified that `--everything` applies only to local references, as the default behavior of 'git lfs migrate' is to never require a force-push unless asked to do so explicitly. --everything sounds dangerous enough that it would imply that a user wants _everything_ in their repository migrated. So, let's loosen the requirement and make it mean that. Alternatively, we could change the meaning of `--everything` in this fashion and replace it with `--everything-local`. We could also introduce `--force`, leave the meaning of `--evrything` unchanged, and only exhibit this behavior with `--everything --force`. Both of these options add too much surface area and complexity for use cases that seem less-common, and/or could be accomplished with clever `git for-each-ref` and `xargs`-ing. [1]: https://github.com/git-lfs/git-lfs/issues/2984 [2]: https://github.com/git-lfs/git-lfs/issues/3118 |
||
|---|---|---|
| .. | ||
| api | ||
| man | ||
| proposals | ||
| custom-transfers.md | ||
| extensions.md | ||
| linux-build.md | ||
| README.md | ||
| spec.md | ||
Git LFS Documentation
Reference Manual
Each Git LFS subcommand is documented in the official man pages. Any of these can also be viewed from the command line:
$ git lfs help <command>
$ git lfs <command> -h
Videos
- How to Work with Big Files - Quick intro to Git LFS.
Developer Docs
Details of how the Git LFS client works are in the official specification.
Details of how the GIT LFS server works are in the API specification.