Hi,

I need help bring the kernel update workflow into Codeberg.

Our CI server automatically builds kernel packages that are found on the
'kernel-updates' branch. This ensures that users will usually not have
to build the kernel packages, which are relatively expensive builds.

The first round of kernel updates I did on Codeberg went okay, not
great. I did this:

$ git push origin contrib-linux-libre:refs/for/kernel-updates -o topic="kernel 
updates" -o title="2025-05-22 kernel updates" -o description="More kernel 
updates"

It made a pull request. It did not put the commits on the
'kernel-updates' branch, but instead the 'lfam/kernel-updates' branch,
so CI did not build them. So, I also pushed them to 'kernel-updates' and
that was good enough.

Now, for the 2nd round of updates, it does not work. I force pushed the
'kernel-updates' branch with the new kernels, based on master. Okay.

But creating the pull request does not work:

------
$ git push origin contrib-linux-libre:refs/for/kernel-updates -o topic="kernel 
updates" -o title="2025-05-29 kernel updates" -o description="More kernel 
updates"
Enter passphrase for key '/home/leo/.ssh/codeberg': 
Enumerating objects: 14, done.
Counting objects: 100% (14/14), done.
Delta compression using up to 4 threads
Compressing objects: 100% (10/10), done.
Writing objects: 100% (10/10), 2.94 KiB | 2.94 MiB/s, done.
Total 10 (delta 8), reused 0 (delta 0), pack-reused 0 (from 0)
remote: 
remote: Forgejo: Unexpected ref: refs/for/kernel-updates
To ssh://codeberg.org/guix/guix.git
 ! [remote rejected]         contrib-linux-libre -> refs/for/kernel-updates 
(pre-receive hook declined)
error: failed to push some refs to 'ssh://codeberg.org/guix/guix.git'
------

What does the pre-receive hook do? I can't figure out where it is
configured for our repository.

Is the problem that I re-used the topic?

Thanks for your help.

Reply via email to