Hey,

Thanks for the report. My guess is that we don't handle the root commit correctly here, which is why this occurs. I'll mark it as a bug and see if we can fix it.

Hey @bk2204 ,

Thank you for responding. I have done a further investigation that might help. I have tried to create a txt file through a git bash to see if it will be also reported as LFS file or not. I have done the following steps:

1. cd into an empty folder
2. create a file 't1.txt'
3. open git bash and run the following :
   1- echo dummy > t2.txt --> that will create t2.txt file in folder
   2- git init
   3- git lfs track '*.txt'
   5- git add .gitattributes
   6- git add.
   7- git commit --m "commit"
   8- git lfs ls-files --> I can see only t2.txt is reported which was created through the GIT bash

Do u think there is any workaround I can do for now to avoid that problem without the need of creating files through git bash?

Ah, I see what the issue is. If the file is empty, then it's not reported. I don't think this has anything to do with Git Bash because I can also reproduce it on Linux as well.

Ah, Okay Thank u for that. Creating the file with content has fixed my problem.
I also need to apply the lockable attribute to the non-empty file to convert it to read-only but that is not happening. I have tried the same steps above but added git lfs track '*.txt' --lockable :

cd into an empty dir
create non-empty t1.txt file
git init
git lfs track "*.txt"
git lfs track "*.txt" --lockable
git add .gitattributes
git add .
git commit --m "Add Files"
git check -attr lockable t1.txt -> shows that the lockable attr is set. But when I open the file on disk. I can edit it. its permission has not changed to read-only.

Hey,

Setting --lockable for a file doesn't change the permissions. That's only the case when you run git checkout (or git clone) for a repository, or use git lfs checkout or git lfs pull. If you want that file to have read-only permissions before you change the branch, then you need to set them in the working tree.

This is because you don't have to use git lfs track; you could simply modify .gitattributes directly. It would be pretty inefficient to update the files on every commit when there's no expectation that the files have in fact changed.