Git-lfs: git lfs is not tracking files that meet specification

Created on 23 Apr 2018  路  1Comment  路  Source: git-lfs/git-lfs

Hi,

git lfs isn't tracking files that meet my specification.

I followed these instructions to the letter: [https://git-lfs.github.com/]

Here's my command output... note the lack of output on the final line.

After the initial failure documented below, I tried the git lfs migrate command suggested in another issue. I got the same warning on a git push after I removed and re-added the file.

user@user MINGW64 ~/repos/repo1 (master)
$ git lfs install
Updated git hooks.
Git LFS initialized.

user@user MINGW64 ~/repos/repo1 (master)
$ git lfs track ".csv"
Tracking "
.csv"

user@user MINGW64 ~/repos/repo1 (master)
$ git add .gitattributes

user@user MINGW64 ~/repos/repo1 (master
$ git status
On branch master
Your branch is up to date with 'origin/master'.

Untracked files:
(use "git add ..." to include in what will be committed)

    table.csv

nothing added to commit but untracked files present (use "git ad

user@user MINGW64 ~/repos/repo1 (master
$ git add table.csv

user@user MINGW64 ~/repos/repo1 (master
$ git commit -m "adding large CSV file, tracked with git lfs"
[master 8920484] adding large CSV file, tracked with git lfs
1 file changed, 1000000 insertions(+)
create mode 100644 table.csv

user@user MINGW64 ~/repos/repo1 (master
$ git push
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 18.26 MiB | 2.22 MiB/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: Resolving deltas: 100% (1/1), completed with 1 local obj
remote: warning: GH001: Large files detected. You may want to tr Storage - https://git-lfs.github.com.
remote: warning: See http://git.io/iEPt8g for more information.
remote: warning: File table.csv is 69.21 MB; thisGitHub's recommended maximum file size of 50.00 MB
To https://github.com/repo.git
eec2587..8920484 master -> master

user@user MINGW64 ~/repos/repo1 (master
$ git lfs ls-files
`

Most helpful comment

Solved. For some reason, .gitattributes was getting lost on the commit. I removed the large file, committed .gitattributes on its own, then re-added and committed the large file. No warning this time on the git push.

>All comments

Solved. For some reason, .gitattributes was getting lost on the commit. I removed the large file, committed .gitattributes on its own, then re-added and committed the large file. No warning this time on the git push.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

danielbayley picture danielbayley  路  4Comments

vtchalakov picture vtchalakov  路  4Comments

lacombar picture lacombar  路  3Comments

kaixin-bai picture kaixin-bai  路  3Comments

sauhaardac picture sauhaardac  路  4Comments