Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: lfs tracking #2269

Closed
yiranwu0 opened this issue Apr 4, 2024 · 2 comments
Closed

[Bug]: lfs tracking #2269

yiranwu0 opened this issue Apr 4, 2024 · 2 comments

Comments

@yiranwu0
Copy link
Collaborator

yiranwu0 commented Apr 4, 2024

Describe the bug

Each time I pull, I see several png files being modified locally and I cannot revert the change. I believe it is due to the github large file system used.

Also, there are two .gitattributes file, one in local and one in website folder, I don't know if that is intentional, or the one in the website folder should be removed? @davorrunje

Steps to reproduce

The composio-autogen.png is not in lfs

(base) kevin@zens-MacBook-Pro autogen % git lfs ls-files | grep "composio-autogen.png"

(base) kevin@zens-MacBook-Pro autogen % git status
On branch main
Your branch is up to date with 'origin/main'.

Changes not staged for commit:
  (use "git add/rm <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   test/test_files/test_image.png
        deleted:    website/.gitattributes
        modified:   website/static/img/gallery/composio-autogen.png

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        website/docs/topics/groupchat/

no changes added to commit (use "git add" and/or "git commit -a")
(base) kevin@zens-MacBook-Pro autogen % git restore website/static/img/gallery/composio-autogen.png
Encountered 1 file that should have been a pointer, but wasn't:
        website/static/img/gallery/composio-autogen.png

Model Used

No response

Expected Behavior

No response

Screenshots and logs

No response

Additional Information

No response

@davorrunje
Copy link
Collaborator

@kevin666aa they should be removed, thanx for figuring this out!

@ekzhu
Copy link
Collaborator

ekzhu commented Apr 4, 2024

Fixed #2270

@ekzhu ekzhu closed this as completed Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants