Z572 <[email protected]> writes:

> Christopher Baines <[email protected]> writes:
>
>>
>> I'll use the new terminology to describe this, but one idea I was
>> looking at previously was not having stateful branches, but instead
>> generating branches from groups of Pull Requests. I think this would
>> make it much easier to manage what changes are going together on a
>> branch, leaving combining and testing these changes to QA.
>
> I think this might be the merge queue of GitHub[1]. NixOS seems to be
> using this: https://github.com/NixOS/nixpkgs/queue/master. However,
> unfortunately, Codeberg does not support this, and we do not use merging
> for the merge process.

I don't know much about it, but from the looks at it this is more about
automatically testing and merging changes in sequence.

What I want is similar, but rather than working sequentially, batch the
changes together for testing. It's infeasible to follow the sequential
approach and build all the packages if each of the changes affects lots
of packages, and it's left down to people to link together any failures
and the potential cause and then remove or fix that before re-testing.

Both I think would be valuable to have though.

Attachment: signature.asc
Description: PGP signature

Reply via email to