| 13 Apr 2023 |
 vcunat | (Though of course, there are cases where you know what you're doing.) | 08:58:59 |
 Artturin | https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging | 09:00:18 |
| Artturin | Afaik there's no way to block on a specific check | 09:04:35 |
| Artturin | 
Download 71f7adbd-f2a4-4444-8b8f-e4896f4c217c.jpeg | 09:07:33 |
 7c6f434c | Well, OfBorg is very conservative with red… | 09:08:16 |
| Artturin | Looks like it's possible | 09:09:27 |
| Artturin | 
Download 9adc2cdc-11f0-4f1c-8727-6a649db73a66.jpeg | 09:09:30 |
 Sandro | I just got an idea: if we only block merge in the presence of a mass rebuild and ignore the absence completely, it would work | 09:46:14 |
| Sandro | In reply to @7c6f434c:nitro.chat
Well, OfBorg is very conservative with red… I am talking about this for months if not a year already: failed pipelines should be red instead of grey. If people don't know how to fix it, they should mark the package broken. Also saves hydra resources. | 09:47:02 |
 tea | In reply to @k900:0upti.me
You can still merge even if it's red yes. we should make more checks red imo but a bit off topic | 09:48:02 |
| 7c6f434c | If you make build failures red now, you'll get timeouts red. | 09:49:56 |
