Mmadu Manasseh

> [@MeNsaaH](https://github.com/MeNsaaH), do you know the reasoning behind this particular logic for `KUBECHECKS_MONITOR_ALL_APPLICATIONS`, where setting it to `false` does not initialize the VCS? Hmmm! IIRC, the earlier versions of kubechecks...

@leoluz At the time the fix was implemented, using dryrun=client was [the best available solution](https://github.com/argoproj/argo-cd/issues/13874#issuecomment-1896203996). However, we're now facing a new issue: running argocd app sync --dry-run --server-side isn't behaving...

Hi folks! is there any traction on this release? this issue is still recurring on my end with EKS `v1.31.7-eks-473151a` nodes running lots of workloads More context: this issue happens...

/remove stale

> I'm wondering (if you don't mind) why this fetch was initially introduced, why not just clone the branch directly as it is done with the non-shallow clone? as @djeebus...

i've reopened this issue. Happy for anyone to pick this up and implement it as well :)

> But I think this feature should cut at the application level (like [this](https://cdn.zappy.app/109825b4f7850895c6c35b184a2585d8.png)), or at least trim at the object level like the issue is with github, the max...

@Greyeye it's all ready now. when you get sometime could you test and review

> It also works for us, [Greyeye](https://github.com/Greyeye) / [djeebus](https://github.com/djeebus). apologies for pinging you like this but it would be great to merge this I'm seeing some cases where this causes...

what's your argocd setup? helm, kustomize etc. so, that we can narrow down the issue. We rolled out a fix for this in https://github.com/zapier/kubechecks/pull/395.