| 28 Feb 2025 |
 maralorn | I made sure that this standard is not iterm2 specific. | 19:28:15 |
| maralorn | I remember back then, that I linked the doc which contained the most actionable information. | 19:30:02 |
 Sandro 🐧 | but you are syncing commits? so git tags should be synced, too, right? | 21:50:30 |
| Sandro 🐧 | I mean since you need to contribute to github anyway, that doesn't make that much sense | 21:53:01 |
| Sandro 🐧 | btw https://github.com/maralorn/nix-output-monitor/pull/181 | 21:55:52 |
| maralorn | I am syncing commits. Not sure about the tags. | 21:55:52 |
| maralorn | Excellent, thanks! | 21:57:23 |
| Sandro 🐧 | at least gitea has no support for tags .... | 21:58:41 |
| Sandro 🐧 | gitlab does | 21:59:13 |
| maralorn | I am relatively certain that forgejo supports tags. | 22:03:26 |
| maralorn | https://code.maralorn.de/maralorn/nix-output-monitor/tags | 22:03:45 |
| maralorn | lgtm | 22:03:47 |
| Sandro 🐧 | 🤔 could be that it only triggers on commits and when you push the next commit the other refs like tags are synced, too? | 22:05:12 |
| Sandro 🐧 | at least both don't mention it in the settings but forgejo in the docs | 22:05:22 |
| maralorn | I do not auto-sync. | 22:12:24 |
| maralorn | And I actually sync via forgejo. | 22:12:41 |
| maralorn | * And I actually sync via jujutsu. | 22:12:47 |
| maralorn | Could be that it does not sync tags. | 22:12:56 |
| maralorn | Huh, it does. | 22:13:40 |
| maralorn | As a matter of fact all but the last tag have been synced to github. | 22:14:36 |
| Sandro 🐧 | just be careful that you don't delete things again 😜 | 22:53:30 |
| Sandro 🐧 | I will leave my fingers of jj. It didn't solve any of my problems and just created confusion lol | 22:53:55 |
| Sandro 🐧 | I need the workflow the other way around: symlink me a branch into this branch and rebase it | 22:54:11 |
| Sandro 🐧 | probably through having some git trailer with a ref to the original branch and commit and re-cherry-pick it on rebase | 22:54:44 |
| 3 Mar 2025 |
 hexa | drumroll | 00:24:07 |
| maralorn | In reply to @hexa:lossy.network
drumroll Waiting for a release? | 00:32:22 |
| hexa | teasing | 08:05:42 |
| hexa | not seeing build time estimations yet 🤔 | 08:06:00 |
| hexa |
⏵ python3.12-mypy-1.15.0 on [1] ⏱ 3m40s (∅ 21m16s)
| 08:32:36 |
| hexa | here we go | 08:32:37 |
