> This is kind of where things are at with hydra channels. Hydra currently *polls* master periodically, whereas with this github *pushes* to hydra/travis/etc, and they git push back to master if the PR passes. This distinction is really important if we want to never break master.
The catch is that it would effectively require serializing the merge > queue's test runs... But most PRs are independent/commute, and we cache well enough to take advantage of that, so I don't think we will need any special tricks here. Anyways I started a thread on exactly this and more https://www.mail-archive.com/nix-dev@lists.science.uu.nl/msg18287.html
_______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
