Devin Canterberry

There may be other reasons why the completion of asdf-flutter has been so delayed (e.g: it does not have a "champion" pushing it through). Here, it looks like we have...

Consider this issue #37 a PSA and Call for Maintainers. I defer to the present maintainers and stakeholders in asdf-community, asdf, and Yarn, for selecting, sourcing, and/or vetting candidates, and...

I've started maintaining a dedicated Helm repo for this chart for those who prefer to install it via a GitHub-owned domain: ```shell $ helm repo add docker-registry https://twuni.github.io/docker-registry.helm $ helm...

I'ved added you both to the project with **Maintainer** permissions. Thanks for volunteering! You're welcome to contribute in any way you're comfortable, as little or as much as you'd like....

> @vyas-n @canterberry What does the release process look like? > > From what I can tell we just need to add a chart tar to the gh-pages branch, but...

@joshsizer > I was wondering if there was any good solutions to keep using `helm.twun.io`, but still delegate releases? Two options come to mind: * Set up a **permanent redirect**...

Quick update: I ran a pilot of the second option above on a separate, temporary domain, with success. I'm working on the next step now, applying that to https://helm.twun.io. In...

@joshsizer This work is now complete. https://helm.twun.io is now a passthrough proxy for https://twuni.github.io/docker-registry.helm and can be updated via the `gh-pages` branch.

Ah. I think the issue might be that the workflow is running in the context of the **target** repo+branch (vs the base PR's branch).

:bulb: FYI: I've temporarily disabled this workflow since we have a few PRs going and `main` and `v2.2.1` are currently failing when using the action's test values (fixed in #77)....