Hi, "devmsv" <m...@posteo.org> writes:
> - Do Guix developers just hack in ~/src/guix, add their own > packages/updates, and commit them later? in this case: > > - How do they deal with channel authentication, merges, and rebasing > with Guix’s master branch? Yes, I think this part is documented here: https://guix.gnu.org/manual/devel/en/html_node/Building-from-Git.html But please let us know if that leaves questions unanswered. > - Is there anything like git bisect but for guix channel? so I can get > what commit (in guix) broke my channel and know how to fix it. No, there’s no ‘guix bisect’. However, the CI systems keep track of it. For instance, if you find a broken package, ci.guix.gnu.org may have information as to what commit range broke it, as in this example: https://ci.guix.gnu.org/build/14223070/details > - How to deal with broken package builds? They are catched by the CI > system: should be report them? why doesn't guix maintain a develop > branch and use master for changes that pass CI? There’s https://qa.guix.gnu.org/patches but unfortunately this system, which does a very good job, was designed for the email-based workflow and has yet to be adapted to Codeberg. The situation is dire though: without proper CI on pull requests, things break and people just notice after the fact. This is frustrating. In the meantime, one option is to provide a stopgap using Cuirass: https://codeberg.org/guix/maintenance/pulls/28 But really, we need people to get onboard to help provide CI for pull requests; the situation is not sustainable. See also the thread at <https://lists.gnu.org/archive/html/guix-devel/2025-08/msg00111.html>. Ludo’.
