Mike Dame

Hi! Have there been any updates on this? It would be very helpful for our project

You might want to open this issue against github.com/kubernetes/kubernetes, the code in this repo is just synced from there so I don't think issues in this repo get much attention

@gjtempleton please keep us updated on what your workarounds are! I would love to continue using this official Helm action if possible, but the automated git push will cause it...

Both sound like great improvements to the action, though for our use case we would prefer the PR option (since every branch in the Kubernetes org needs to have branch...

@unguiculus that's a good question, and I actually didn't think of that (my mistake). But based on what they're trying in [autoscaler](https://github.com/kubernetes/autoscaler/pull/3403#issuecomment-668595073), the branch becomes protected after the first push,...

@stevehipwell I have been manually modifying the branch protection to allow for the release to run. getting the release to run automatically (with branch protection) is still a TODO for...

@stevehipwell oh awesome, thanks for the tip! I'll give that a try

Would it be a breaking change to make the namespace include/exclude fields a regex? Current settings with alphanumeric namespace strings would still only match the exact name, so the functionality...

Hi @unacceptable Just curious, have you tried solving this with preemption and found that it wasn't working for you? I ask because this still sounds like something that preemption in...

This looks ok, I just want to learn a little more about the `go-runner` binary before we wrap our command in it for every build (especially given the recent issues...