commit | 76a4a9df86e9f969caf1fdd9e6d2f3ec5f18e94f | [log] [tgz] |
---|---|---|
author | David Pursehouse <dpursehouse@collab.net> | Tue Aug 16 12:11:12 2016 +0900 |
committer | David Pursehouse <dpursehouse@collab.net> | Tue Aug 16 21:55:36 2016 +0900 |
tree | 6ad547c43b522e8f6df7fbd6a07d4cced9a692a7 | |
parent | befaec1e56e70582249f6cd4a5f9de5c012ad718 [diff] |
project: Set config option to skip lfs smudge filter During sync, repo runs `git read-tree --reset -u -v HEAD` which causes git-lfs's smudge filter to run. However this fails because git-lfs does not work with bare repositories. Add lfs.filter configuration to the project config as suggested in the comments on the upstream git-lfs client issue [1]. This prevents the smudge filter from running, and the sync completes successfully. For any projects that have LFS objects, `git lfs pull` must be executed. [1] https://github.com/github/git-lfs/issues/1422 Bug: Issue 224 Change-Id: I091ff37998131e2e6bbc59aa37ee352fe12d7fcd
Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.