Is your feature request related to a problem? Please describe.
Prevent issues like #7669 by building the whole flake before merge.
Describe the solution you'd like
Maybe Theophane was right. I could add a bors.toml after an admin installs Hercules CI and bors on this repo. Instead of "enable auto-merge", we'd comment bors r+ to indicate a positive review and let bors merge it as appropriate. This way we build a larger set and we get the guarantee that the merge builds. (informally: the no rocket science rule)
Bors also allows the delegation of review (merge) rights to contributors, and it does not suffer from the GitHub Actions limitation on builds triggered by actions.
Describe alternatives you've considered
Extend the actions, but they seem slow. Doesn't help with NixOS tests either. I don't know a ton about actions, whereas the above is easy and you'll get amazing support.
Additional context
Add any other context or screenshots about the feature request here.
Priorities
Add 👍 to issues you find important.
Is your feature request related to a problem? Please describe.
Prevent issues like #7669 by building the whole flake before merge.
Describe the solution you'd like
Maybe Theophane was right. I could add a bors.toml after an admin installs Hercules CI and bors on this repo. Instead of "enable auto-merge", we'd comment
bors r+to indicate a positive review and let bors merge it as appropriate. This way we build a larger set and we get the guarantee that the merge builds. (informally: the no rocket science rule)Bors also allows the delegation of review (merge) rights to contributors, and it does not suffer from the GitHub Actions limitation on builds triggered by actions.
Describe alternatives you've considered
Extend the actions, but they seem slow. Doesn't help with NixOS tests either. I don't know a ton about actions, whereas the above is easy and you'll get amazing support.
Additional context
Add any other context or screenshots about the feature request here.
Priorities
Add 👍 to issues you find important.