ApplicationSet controller "unable to resolve git revision" for new branches - any way to trigger a refresh?

[aaron-lunsford-even]

Hey folks, got a question: We have a pipeline that executes on merge requests and runs an argocd appset generate command against the source branch and target branch of the merge request, compares the results, and outputs a diff to the user.

When the pipeline runs shortly after the source branch has been pushed to the repository, the argocd appset generate command often fails with unable to resolve git revision because the branch is new. We have a retry built into the pipeline because eventually the command will succeed, but it would be nice to not rely on such a mechanism as it is brittle and can take take quite a few retries before it succeeds.

I'm assuming it's the repo server that's responsible for tracking branches against the repository and I haven't been able to find a way to trigger a refresh/fetch/whatever to tell it to get the latest branches. Is anyone aware of a way to programmatically tell the repo server (or whatever the appropriate workload might be) to update its list of known branches?

[aaron-lunsford-even]

Figured this out. The RepoServerServiceClient interface has a method called GetGitFiles, and the request options you can pass to it include a NoRevisionCache field that, when set to true, will trigger a cache refresh and get the latest refs.