| 21 Nov 2022 |
 hexa | and after the rebase the commit had a new hash 🤷 | 21:03:45 |
 VladimÃr ÄŒunát | Ah... well master tends to move fast. | 21:03:53 |
| hexa | yeah | 21:03:57 |
| VladimÃr ÄŒunát | Could add to the checklist that you should push commit first before tagging it. | 21:04:17 |
| hexa | yeeh, planning to go through the tasks once more and clean things up | 21:04:46 |
| hexa | * yeah, planning to go through the tasks once more and clean things up | 21:04:49 |
| 22 Nov 2022 |
 sterni | https://github.com/NixOS/nixpkgs/pull/180964#issuecomment-1324188963 has anyone ever seen this happen? seems like it worked fine, but it should not try to push to release-21.11, right? | 20:20:36 |
| 23 Nov 2022 |
| hexa | the workflow produces those errors quite often | 11:17:43 |
 Janne Heß | while ! git push …; do sleep .1; done | 11:18:11 |
 infinisil | There's both https://malob.github.io/nix-review-tools-reports/ and https://zh.fail/, which should be preferred? | 19:41:59 |
| hexa | i think malo's is better maintained 😄 | 19:48:03 |
| hexa | zh.fail shows per maintainer failures | 19:48:17 |
| hexa | zh.fail also still thinks trunk-combined is x86_64-linux only | 19:48:34 |
| Janne Heß | In reply to @hexa:lossy.network
i think malo's is better maintained 😄 As the maintainer of zh.fail I agree | 19:51:46 |
 malo | FWIW, I think the best long term solution would be to make changes to Hydra pages (and the API), to both make it easier to find some of this information on Hydra itself, or at least less cumbersome to create external tools to present information that Hydra doesn't present. | 19:52:05 |
| Janne Heß | In theory yes but it's so unlikely that someone will do this that I think it's fair to say it's impossible | 19:52:56 |
| malo | There has been some effort, though not much. For example something like this PR would be a step in the right direction: https://github.com/NixOS/hydra/pull/1204 | 19:53:25 |
| malo | The main reason I haven't done this myself is because I basically have no familiarity with Perl and the tech used by Hydra. Otherwise I would have just made the changes myself instead of making nix-review-tools-reports (and now working on https://github.com/malob/hydra-tools). | 19:56:11 |
| infinisil | Alright thanks, I guess I'll use a combination of both then :) | 19:57:38 |
| infinisil | Btw I'm preparing a small presentation for the ZHF hackathon in Zürich on Saturday | 19:58:12 |
| infinisil | Talking about how to contribute to ZHF | 19:58:19 |
| 25 Nov 2022 |
| hexa | https://repology.org/repository/nix_stable_22_11 #tada | 14:01:03 |
| hexa | blank slae | 14:01:10 |
| hexa | * blank slate | 14:01:11 |
| hexa | Winter (she/her), Mic92 how you're working on the release notes 🙂 | 16:01:37 |
| hexa | * Winter (she/her), Mic92 how's you're working on the release notes going 🙂 | 16:01:46 |
| hexa | * Winter (she/her), Mic92 how's you're work on the release notes going 🙂 | 16:01:51 |
 Winter (she/her) | 
Download ima_ef0de79.jpeg | 16:06:24 |
| hexa | yeah, the original message was a bit too harsh | 16:06:51 |
| Winter (she/her) | In reply to @hexa:lossy.network
Winter (she/her), Mic92 how's you're work on the release notes going 🙂 i need to respond to the nsncd issue, then sync the notes from branchoff with our copy from a few weeks ago | 16:07:03 |
