feat: show application-added repositories in the repo list

[bianbbc87]

Closes #23720

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Title of the PR
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.
• Optional. My organization is added to USERS.md.
• Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

[bunnyshell]

✅ Preview Environment deployed on Bunnyshell

Component	Endpoints
argocd	https://argocd-eq3hoy.bunnyenv.com/
argocd-ttyd	https://argocd-web-cli-eq3hoy.bunnyenv.com/

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

• 🔴 /bns:stop to stop the environment
• 🚀 /bns:deploy to redeploy the environment
• ❌ /bns:delete to remove the environment

[bianbbc87]

PR Summary

Surface repositories that Applications use in Settings → Repositories to improve visibility and navigation.

This PR re-submits the same changes as #24094
The original PR was closed after the branch was rebased and force-pushed.

Proposal

1. Show linked Applications in the repo list

• Add an “Apps” column showing the number of linked applications.

when retrieving unique repos from applications and when calculating the app count, if a repo in repos contains .git, the comparison with application repos is done using a normalized form where .git is removed.

1.1. when it has .git repository

Regarding point 2,

repo summary links to the filtered app list

it means that in the repo detail view you can check the links for connected apps, and clicking on one of those links will take you to the corresponding application summary page. The flow looks like this:

you can see application links in repository detail view

and click link

• If no apps exist, link to Create Application prefilled with this repo URL.

2. Make unconnected (but app-referenced) repos visible

• In the list, place repositories referenced by Applications but not connected as a Repository at the top.
• Add a Not Registered status badge.
• Duplicates are excluded.

3. Provide actions for “Not Registered” repositories

• In the right-side menu, show Connect Repository and Create Application.

• For Not Registered repos (and when type === 'git'), make the repo detail read-only. Introduce a registered prop to the EditPanel to track this state (avoids misusing noReadonlyMode, which showed irrelevant inputs).

4. Keep existing list behavior consistent

• Search and filters work across all items, including Not Registered.
• A horizontal divider separates Not Registered items from the rest; it disappears if none exist.

5. Project filter expansion

• Expand project filtering from “the repo’s own project” to all projects. This fixes the case where application-sourced repos didn’t display a project and improves visibility.

Full

2025-08-10.8.16.39.mov

Discussion

1. Non-git types don’t have a repo detail view, so we can’t show the “linked apps” link. Is this acceptable?
2. The action menu differs by connection status. Is this clearer or potentially confusing?

• Not Registered: Connect Repository, Create Application
• Registered: Create Application, Disconnect

3. I added oci to the repo type filter because it wasn’t being filtered; does anyone know why oci was missing originally?