if approved, i am willing to provide pr.

This seems like a bit of a UX challenge. What would the presentation of 2 revisions look like? Of 5?

@crenshaw-dev

ArgoCD versions 2.10 and below have reached EOL. Can you upgrade and tell us if the issue is still present, please?

Hi! Yes, it is present in the greatest latest. Maybe next time it'd be nice if you could just a run a quick check yourself, it'd just a matter of reading the bug report and clicking on the code segment linked in the description which points to master. I understand that doing auto-triage is useful as there's a big backlog of issues, but it's also a bit annoying for reporters.

While I'd generally agree with you, I'm going through ~1600 bugs manually, so can't check every one of them. That's where I rely on the community help. Please, be understanding.

Any update on this? I don’t think it needs to be overly complex. For most people, it would be enough to show the revision in a badge for the first defined source in a multiple-source setup.

For example, when using Helm with external values, I’m not really interested in the revision of the values, but I’m definitely interested in the targetRevision of the Helm chart to be shown in badge.

It follows the same principle as how you want your application to be previewed in the UI. If you define external values as the first source, the application will be displayed as a Git repository. If you define the chart first, it will be shown as a Helm release.