Michael Crenshaw

This PR is currently a hacky mess. But it provides basic write credential handling (UI and backend) and a basic UI for the hydrator, built into the application view.

hydrator(ui): refresh revision metadata in hydrator panel

1

The source hydrator panel contains dry commit metadata. When the hydrator is refreshed, and a new commit is handled, the metadata still shows the info for the old commit. This...

feat(hydrator): add sourceHydrator types

3

I'm breaking the hydrator into separate PRs. This is party to make them easier to review, partly because the commit history on the original PR is pretty messy at this...

I'm breaking the hydrator into separate PRs. This is party to make them easier to review, partly because the commit history on the original PR is pretty messy at this...

feat(hydrator): add commit-server component

2

I'm breaking the hydrator into separate PRs. This is party to make them easier to review, partly because the commit history on the original PR is pretty messy at this...

chore(cmp): refactor and test plugin discovery

7

Plugin discovery logic is complicated and has resulted in [difficult to diagnose bugs](https://github.com/argoproj/argo-cd/pull/20196). This PR makes a few changes: 1) Deprecate `RepositoryResponse.IsDiscoveryEnabled` field. No code actually uses that field anymore...

feat(ci): run UI e2e tests

7

Looked the the ui-test directory was mostly going unused. I got the tests working in CI, so hopefully that'll make the tests more useful.

Drop support for `applications.argoproj.io/app-name`

5

# Summary Remove support for old tracking label, `applications.argoproj.io/app-name` # Motivation `"applications.argoproj.io/app-name"` is found once in the argo-cd repo: ```go // LabelKeyLegacyApplicationName is the legacy label (v0.10 and below) and...

chore: improve comments describing different refresh levels

1

Checklist: * [ ] Either (a) I've created an [enhancement proposal](https://github.com/argoproj/argo-cd/issues/new/choose) and discussed it with the community, (b) this is a bug fix, or (c) this does not need to...

In today's Maintainers' meeting, we realized the SIGs need to designate "secretaries" to be responsible for SIG communication to the broader maintainer community. Pasha volunteered and has the support of...