BUG - Auto Pull Operation of Repositorys with LFS enable dont´t Sync New LFS Content

[NicholasRush]

Description

Hello everyone,

i currently have two LXC instances running with Gitea. Both in the internal network with a self-signed certificate. Instance 1 is my "work instance" on which I am actively working. Instance 2 (offsite) pulls the repos I am working on from instance 1. This works so far. But now I have started using Git-LFS in some repos. And that is where the problem comes in. When initially pulling a repo, it creates all the LFS data of the repository in the LFS storage of instance 2 in addition to the LFS indexes. However, if data is then added to the repository, it no longer syncs this LFS data, just the repo data itself. The whole thing can be fixed by deleting the corresponding "pull" repos on instance 2 and creating new ones. But that is not the point of the matter. I don't want to work in a single instance either, because the work instance (instance 1) actually only contains projects that are actively being worked on.

Gitea Version

1.23.1

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

git version 2.39.5

Operating System

Debian Linux 12.9

How are you running Gitea?

LXC - Container

Database

MySQL/MariaDB