jeff-knurek

I found out a way to reproduce this. One thing that seems to be helpful in reproducing is having more than one dependency in the requirements file. Also, the large...

/remove-lifecycle rotten

@edmacabebe I think the documentation you might be looking for is in the helm chart. Specifically https://github.com/helm/charts/tree/master/stable/sonatype-nexus#recommended-settings in particular the `ingress` and `nexusProxy` values.

an `alpine` based image would be great to have. 👍 currently our `cypress` image is the only one we run on k8s that has vulnerabilities. And basing an image on...

@kleini `checkout scm` has an option for setting a LFS pull, `[$class: "GitLFSPull"]`, have you tried that with your workaround? ---- even if you do, I expect you might still...

hmmm... I tried with a new chart and it worked fine, but modified an existing chart that throws an error with the above example and I get: ``` Validating maintainers......

ok, I managed to get some commands to reproduce `docker run --rm -it --entrypoint=/bin/sh quay.io/helmpack/chart-testing:latest` _(where latest is v2.4.0)_ ``` git clone https://github.com/kubernetes/charts.git cd charts/ # this should work because...

@RonaldCrb @unguiculus any thoughts on this? Should I work on a PR to disable this VCS name check?

> The whole point of this check is to make sure the accounts exist. And this is where myself, and at least @batazor disagree. There's nothing in the [helm documentation](https://helm.sh/docs/topics/charts/#the-chartyaml-file)...

> Seems like GitHub/Bitbucket/GitLab username should be a separate field fully agree, though I think that would be a bigger change to happen in `helm`. But the _idea_ behind such...