Alexandre Gaudreault

In the meantime, can we get a fix in `0.5.X` to do what the documentation is saying and remediate to the issue until something more bulletproof is implemented in 0.6.0...

The reason this broke without updating `argocd-notifications` is because it calls the `argocd-repo-server` service to get the information and it is actually that services peerforming the call and failing. https://github.com/argoproj-labs/argocd-notifications/blob/c461d624b4c02452e85821361bb1c4c2d2e487b7/shared/argocd/service.go#L74...

For reference, we have the same problem and our ArgoCD instance is configured on our private repositories with credential template and a GitHub app according to https://argo-cd.readthedocs.io/en/stable/user-guide/private-repositories/#github-app-credential. (Using 2.1.3) ```...

After upgrading to v1.2.1 with argoCD v2.2.3, I am able to use `.repo.GetCommitMetadata`.

This should probably be closed by now, but on my side I had the wrong `clientId` 😓 So I would suggest to anyone that stumble upon this to decode their...

You are right. `onEnterWaiting` does not matter much in this scenario because the SCM is not present on the job so it won't publish anything. However, after the first `checkout`...

I think these can be 2 different problems. If the `GitSCMChecksContext` uses the first build data only, then it should respect the associated `GitSCMStatusChecksExtension` configuration of this build data. If...

We have the same bug and it is caused by our global library being loaded at the beginning of the build. The SCMFacade will return the Global Library SCM instead...

This approach would help for commands like `publishChecks` as well because we could send the `scm` hint as parameter, but for the global checks, I think if the config is...

@jeffrichie we are running this fork on our CI for quite some times, it works the way it is intended to! But the maintainers does not seem thrilled to the...