Eoin Motherway

Is there any progress on this? I've got a fork that builds on this PR, happy to submit it here if it's of any value.

Bump. Is there anything I can do to help progress this further?

@VinnyOG We haven't gotten around to making use of this. Our use-case requires a new build of LibGit2Sharp, which proved to be too much of a pain.

I've mucked up the rebase and the PR auto-closed... 🤦 Doesn't seem to let me re-open it, so I've created a new one over here https://github.com/libgit2/libgit2/pull/6394 Sorry for the mess...

Still getting this issue on 36.2.0

A workaround I've found is to move the config into a custom resource definition, and reference that using `alertmanager.alertmanagerSpec.alertmanagerConfiguration`. Example: ```yaml # receiver-config.yaml apiVersion: monitoring.coreos.com/v1alpha1 kind: AlertmanagerConfig metadata: name: alertmanager-config...

@jsalatiel That _should_ work. What I've found is that you need to install the chart first so that he CRDs get added, apply the custom `AlertmanagerConfig`, then re-install/upgrade the helm...

> Have you tried creating an Octopus Server PR that uses this build? To see if anything has broken/changed because of this? Octopus branch here with the changes: https://github.com/OctopusDeploy/OctopusDeploy/pull/8357 Tested...

It looks like this can be achieved using the theme context tag: https://github.com/anuraghazra/github-readme-stats#use-githubs-theme-context-tag I'll go ahead and close this off for now.

`git pull` is not the same as creating a pull request. ([Docs](https://www.git-scm.com/docs/git-pull)) _"Pull requests"_ are no native to `git`, they are a concept provided by each individual git provider. GitHub...