Repository navigation
Conversation
This run the pr-if-new-kernel workflow as well for the branches rel-1877 and rel-2150. To open PRs in case a new kernel was released. Signed-off-by: Tobias Jungel <1773291+toanju@users.noreply.github.com>
55503e6 to
9cca48b
Compare
|
Hi and thank you for your contribution! The way our setup works right now is: we have the new PRs whenever the kernel is updated. We can check if the kernel compiles on update-6.12 and update-main before anything gets merged. Once the compilation completes we merge the update- branches to the maint-* branches. And once we make a release, we then cherry pick or merge the maint-6.12 and maint (for 6.18.) to our rel-* branches, because we then keep more control over when and what we release. New commits / merges on rel-* automatically means a new package is built. |
|
Since gardenlinux/package-build@fbdfe6b one would have the chance to build already in the PR, so maybe it's worth to have that integrated to speed up a little? In addition, 6.12.113 is out and the auto-PR currently fails like https://github.com/gardenlinux/package-linux/actions/runs/39203626406/job/117901634569 which makes me wonder if something like Renovate should be taken into account? (and yes, the problem is resolved by now) |
This run the pr-if-new-kernel workflow as well for the branches rel-1877
and rel-2150. To open PRs in case a new kernel was released.