-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
File upload doesn't respect .gitattributes to put the file in LFS #18297
Comments
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Jan 17, 2022
We need to use the cached .gitattributes file for checking if a file should be stored in the lfs. Fix go-gitea#18297 Signed-off-by: Andrew Thornton <[email protected]>
zeripath
added a commit
that referenced
this issue
Jan 18, 2022
We need to use the cached .gitattributes file for checking if a file should be stored in the lfs. Fix #18297 Signed-off-by: Andrew Thornton <[email protected]>
Chianina
pushed a commit
to Chianina/gitea
that referenced
this issue
Mar 28, 2022
We need to use the cached .gitattributes file for checking if a file should be stored in the lfs. Fix go-gitea#18297 Signed-off-by: Andrew Thornton <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Gitea Version
1.15.8 and 1.16.0_dev_850_ga38ab71b20
Git Version
2.34.1
Operating System
Linux
How are you running Gitea?
I'm using the Arch Linux package for gitea and running it through the systemd service provided by the package.
Database
PostgreSQL
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/baltitenger/d048c3b523cc44969ad3f21c294b26a0
Description
Uploading files using the web UI ignores
.gitattributes
and adds files to git instead of uploading them to LFS.The issue can be seen in this test repo.
My
app.ini
can be seen in this gist.Perhaps related to #17496
Screenshots
The repo after uploading the file through the web UI:
![image](https://user-images.githubusercontent.com/21960678/149661302-434db829-4726-4415-abf7-c454655807bc.png)
The text was updated successfully, but these errors were encountered: