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 think something like this combined with doing more testing earlier, so > doing at least some building and testing of all branches, not just the > ones about to be merged would greatly improve the situation. [1]: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue
signature.asc
Description: PGP signature
