| 26 Dec 2025 |
 leona | I don't know of any | 15:17:43 |
 Janne | Probably waiting for them to cancel us | 15:17:54 |
 gabyx | cause of too many actions? | 15:18:07 |
 Find me at aleksana:qaq.li | In reply to @gabyx:matrix.org
Wouldn't also be helpful, if one could have some yaml annotation in the PR decscription
which could be taken up in a Github job which could then do some special attribute builds?
Just a simple stupid Nix VM (Github Job) which builds the requested attribute on requested arch (optional) etc.
like ofBorg does but in Github Actions (note: I hate Github Actions to the core..., the worst...) I wonder if github allows you to register some bots to do it yourself, just like the shitty copilot review | 15:18:29 |
| gabyx | the only thing I see with github action VMs is they start pretty fast... | 15:19:01 |
| Janne | Ofborg actually receives most things that happen in nixpkgs from a webhook, one could subscribe to that rabbitmq queue | 15:19:12 |
| gabyx | * the only thing I see with github action VMs is they start pretty fast... and for OSS there is not limit | 15:19:15 |
| gabyx | * the only thing I see with github action VMs is they start pretty fast... and for OSS there is not limit AFAIK | 15:19:20 |
| gabyx | ofborg runs as single binary on a few VMs with different arch? | 15:20:40 |
 emily | fwiw if we get Enterprise then we will have more Actions minutes than we know what to do with | 15:20:55 |
| emily | although the runners are really just incredibly slow | 15:21:01 |
| Janne | It's a surprising amount of components. But one is the webhook receiver which receives webhook events and streams them to a queue. Multiple subscribers can hook to that | 15:21:27 |
