Am Tue, Jul 15, 2025 at 05:13:38PM +0200 schrieb Ludovic Courtès: > How are these commits dropped, concretely? Do they get reverted by the > person in charge of this staging branch?
That is what I understood. In the Guix context, I would rather rebase interactively and drop the commits, but the end result would be the same. > What about per-pull-request builds? My understanding is that those > submitted by the @r-ryantm package upgrade bot¹ are built before being > submitted: > https://github.com/NixOS/nixpkgs/pull/425322 > … but those submitted manually have a number of tests ran automatically > but it’s not clear to me whether that includes actual builds: > https://github.com/NixOS/nixpkgs/pull/425319 > I suppose PRs reach the staging branch after these tests have succeeded, > right? > ¹ https://nix-community.github.io/nixpkgs-update/r-ryantm/#r-ryantm I think you are right. Looking at the manual pull request, it does not seem to be built automatically, I only see the number of dependent packages (equivalent to "guix refresh -l" without the package names). And for the automatic pull request, they have apparently built all depending packages, like our QA does for debbug patches. > In practice, I suspect updates “that go together” would still be > submitted as one pull request, and thus tested independently of the rest > at that point. (Akin to creating a branch and getting QA/CI to build > it, except that this happens automatically.) Maybe. Except that I wonder about the number of commits: When I rebase the core-packages-team branch, it now counts over 500 commits. This is a volume that cannot be treated in a "hit or miss" fashion. > Sorry for bringing more questions. :-) On the contrary; we just had an informal chat, so our discussion was far from reaching an actionable plan for Guix. And I saw it more as a source of inspiration to inform our own project decisions. Andreas
