brickhousewench (
brickhousewench) wrote2025-07-09 06:42 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Entry tags:
I have done a thing!
Probably none of this will make any sense to people, but I'm super proud of myself, so I'm gonna write about it. This is kinda a follow up post to the one I made about a week ago, so maybe go read that one for background?
Our new Helm Maintainers group has been really cranking. To date we have:
* Closed 47 pull requests as already fixed, duplicates, or no longer needed.
* Actually reviewed, updated, and merged 11 pull requests.
Our automation is supposed to release the updated Helm charts once a week, but since the developers weren’t getting around to doing code reviews, we weren’t having any updates, so the guy who set up our automation turned off the weekly releases. Which I kinda suspected after I looked at all the workflows and saw that they hadn’t been triggered in two months. So when out weekly team meeting ended early on Tuesday, I messaged him right after the call ended and asked, since we had twenty minutes free, if he could talk me through the workflows. Because there were five different workflows with “helm” in the name, and I wanted to understand which ones did what.
He talked me through all of them. And I took notes. And after I got off the call with him, I wrote up my notes in a Google Doc and shared it with the two Developer Advocates that I’m working with. Because I’m a technical writer, it’s what I do. And also, we shouldn’t be in a situation where only one guy knows how all this works. Then I was going to knock off for the day. But I’m promised myself (and posted on the Community Slack) that I’d make sure we got a release out on Tuesday. So I pushed the button. And instead of generating a new PR, it updated an existing PR that I didn’t realize was still hanging around (I’d closed a bunch of that were at least two months old). I pinged the developer and he said that was expected behavior. Then I was going to wait until this morning to merge the PR. But I wanted to push the button.
So Reader, I pushed the button.
I could see immediately that the Helm Chart version was updated in our repository. But one of the workflows was to publish the chart to another repo and to the ArtifactHub, which is where people download them from. And I didn’t see it published, even after I cleared my browser cache. I had dinner, checked back, still didn’t see it. Then, when I was really ready to finally shut down for the night and stop watching, the chart in ArtifactHub finally updated.
So I did a thing. Because we hadn’t run the workflows in two months, I wasn’t sure if they were going to work or not (we had a security incident back at the end of April and had to replace all our authorization tokens and I keep finding workflows that we missed, because we haven’t used them since then). But everything worked, just the way it was supposed to. And I published a new set of Helm Charts. Whoo hoo!
Our new Helm Maintainers group has been really cranking. To date we have:
* Closed 47 pull requests as already fixed, duplicates, or no longer needed.
* Actually reviewed, updated, and merged 11 pull requests.
Our automation is supposed to release the updated Helm charts once a week, but since the developers weren’t getting around to doing code reviews, we weren’t having any updates, so the guy who set up our automation turned off the weekly releases. Which I kinda suspected after I looked at all the workflows and saw that they hadn’t been triggered in two months. So when out weekly team meeting ended early on Tuesday, I messaged him right after the call ended and asked, since we had twenty minutes free, if he could talk me through the workflows. Because there were five different workflows with “helm” in the name, and I wanted to understand which ones did what.
He talked me through all of them. And I took notes. And after I got off the call with him, I wrote up my notes in a Google Doc and shared it with the two Developer Advocates that I’m working with. Because I’m a technical writer, it’s what I do. And also, we shouldn’t be in a situation where only one guy knows how all this works. Then I was going to knock off for the day. But I’m promised myself (and posted on the Community Slack) that I’d make sure we got a release out on Tuesday. So I pushed the button. And instead of generating a new PR, it updated an existing PR that I didn’t realize was still hanging around (I’d closed a bunch of that were at least two months old). I pinged the developer and he said that was expected behavior. Then I was going to wait until this morning to merge the PR. But I wanted to push the button.
So Reader, I pushed the button.

I could see immediately that the Helm Chart version was updated in our repository. But one of the workflows was to publish the chart to another repo and to the ArtifactHub, which is where people download them from. And I didn’t see it published, even after I cleared my browser cache. I had dinner, checked back, still didn’t see it. Then, when I was really ready to finally shut down for the night and stop watching, the chart in ArtifactHub finally updated.
So I did a thing. Because we hadn’t run the workflows in two months, I wasn’t sure if they were going to work or not (we had a security incident back at the end of April and had to replace all our authorization tokens and I keep finding workflows that we missed, because we haven’t used them since then). But everything worked, just the way it was supposed to. And I published a new set of Helm Charts. Whoo hoo!