Gerhard

And that's me making sure that I ran it myself on a different machine to make sure that the thing works and how does it work. And sometimes, more often than not, I find issues and I fix them. It's just a more, I don't know, wholesome way of approaching something. And I enjoy it. I think it's more professional way as well. However, I still do commits. Commits have their place.

And that's me making sure that I ran it myself on a different machine to make sure that the thing works and how does it work. And sometimes, more often than not, I find issues and I fix them. It's just a more, I don't know, wholesome way of approaching something. And I enjoy it. I think it's more professional way as well. However, I still do commits. Commits have their place.

So I'm not dissing them. I'm saying, all I'm saying is like different approaches and different contexts and different ways of sharing that information.

So I'm not dissing them. I'm saying, all I'm saying is like different approaches and different contexts and different ways of sharing that information.

You do use a GitHub action. This is, I'm looking at in our changelog repository, GitHub workflows, dagger on namespace. That's the one that I'm looking at. And it's line right now, 68. Announce deploy in Kaizen Zulip. And you're using the Zulip GitHub action, Zulip send message V1. You have an API key, you have the email, organization URL, to type topic content.

You do use a GitHub action. This is, I'm looking at in our changelog repository, GitHub workflows, dagger on namespace. That's the one that I'm looking at. And it's line right now, 68. Announce deploy in Kaizen Zulip. And you're using the Zulip GitHub action, Zulip send message V1. You have an API key, you have the email, organization URL, to type topic content.

I think the content was the interesting one because you had to trim the git sha, you had to use like a short sha. I've seen a couple of commits where you were trying to fix- I was tweaking it. That integration, exactly, yeah.

I think the content was the interesting one because you had to trim the git sha, you had to use like a short sha. I've seen a couple of commits where you were trying to fix- I was tweaking it. That integration, exactly, yeah.

Well, it looks good. It works well. I was very happy to see this. And it's in the Kaizen channel. It's exactly where it needs to be. Code deploys. It's all there. So you can go and check it out. That's very nice. So the one thing which I had to do as a follow-up, pull request 536, right? We have two of everything. We are running the primary deploys through namespace.

Well, it looks good. It works well. I was very happy to see this. And it's in the Kaizen channel. It's exactly where it needs to be. Code deploys. It's all there. So you can go and check it out. That's very nice. So the one thing which I had to do as a follow-up, pull request 536, right? We have two of everything. We are running the primary deploys through namespace.

They run Dagger for us and they run the actual, the CI and CD part as well. But we also run GitHub as a fallback. So what we wanted to do is announce deploys in ZLoop as well on the GitHub runners. So all I did was just basically copy what you've done, Jared, and put it there. The fact that I copied it makes me think that, you know, they should be refactored. They should be simplified in some way.

They run Dagger for us and they run the actual, the CI and CD part as well. But we also run GitHub as a fallback. So what we wanted to do is announce deploys in ZLoop as well on the GitHub runners. So all I did was just basically copy what you've done, Jared, and put it there. The fact that I copied it makes me think that, you know, they should be refactored. They should be simplified in some way.

There's quite a lot of configuration. So it's something for my list. However, we discussed in the last Kaizen the namespace runners and how much will they cost us per month. So now the numbers are in and we get to pick. So option A, it cost 50, 50, yeah, 40 cents. I'm typing this up, 40 cents. So $0.4, that's option one. Option, no, no, no. I went too far. I went too far. Hang on.

There's quite a lot of configuration. So it's something for my list. However, we discussed in the last Kaizen the namespace runners and how much will they cost us per month. So now the numbers are in and we get to pick. So option A, it cost 50, 50, yeah, 40 cents. I'm typing this up, 40 cents. So $0.4, that's option one. Option, no, no, no. I went too far. I went too far. Hang on.

I'm doing this like as a live edit and I don't want to. He's live editing his slideshow. Cool. For those listening. B is $1 and C is $2. How much do you think it cost us per month? 40 cents. A, correct. It was exactly 54 cents.

I'm doing this like as a live edit and I don't want to. He's live editing his slideshow. Cool. For those listening. B is $1 and C is $2. How much do you think it cost us per month? 40 cents. A, correct. It was exactly 54 cents.

Well, out of these options, option A is closest to the reality. I didn't give you the right number. It was, I didn't want to make it 50. It'd be too obvious, I guess. Too obvious, exactly. So maybe I could have done like 0.5. It was, yeah.

Well, out of these options, option A is closest to the reality. I didn't give you the right number. It was, I didn't want to make it 50. It'd be too obvious, I guess. Too obvious, exactly. So maybe I could have done like 0.5. It was, yeah.

Mm-hmm. It's a fast GitHub Actions runner with caching built in and a bunch of features like, for example, Nice UI, which shows you how long your builds are taking, how much CPU they're using, memory using. So you just get more insights into what's happening when the builds run.

Mm-hmm. It's a fast GitHub Actions runner with caching built in and a bunch of features like, for example, Nice UI, which shows you how long your builds are taking, how much CPU they're using, memory using. So you just get more insights into what's happening when the builds run.