-
-
Notifications
You must be signed in to change notification settings - Fork 19
Description
This is the first failing job.
A few days ago my repository has been merged: nix-community/NUR#982
Today I checked the website to see if I could find my packages and I found out that the action here is failing and my repository may be the reason.
In particular I read
2025-09-29T21:39:41.1498997Z Your branch is ahead of 'origin/main' by 2 commits.
2025-09-29T21:39:41.1499842Z (use "git push" to publish your local commits)
2025-09-29T21:39:41.5300116Z HEAD is now at 9f113d2750 update repos.json + lock
2025-09-29T21:39:41.8027526Z Remote "origin" does not support the Git LFS locking API. Consider disabling it with:
2025-09-29T21:39:41.8028462Z $ git config lfs.<unknown>.locksverify false
2025-09-29T21:39:41.8540207Z batch request: missing protocol: "<unknown>"
2025-09-29T21:39:41.8552264Z error: failed to push some refs to 'https://github.com/nix-community/nur-combined.git'
If I understood it correctly this is where the workflow pushes the combined repos to this repository, isn't it? Then why is it complaining about LFS?
The LFS error triggered me because I use git lfs in my repository and in my head it was a good idea specifically for NUR, indeed this way in theory git without lfs is still able to clone the repository without downloading those files (which are not needed to evaluate and build the packages that I export for NUR) while keeping the repository size small.
@Pandapip1 Do you think that this issue should have been opened directly in NUR? If you confirm that my repo is causing this feel free to remove it (sorry people).
@Mic92 I'm kindly tagging also you since you are the maintainer of this repository.