Repository with same name shows double check

[MatHoyer]

To Reproduce

1. Have a git provider configured (in my case gitea)
2. Have 2 repo named the same way but in 2 organizations for example
3. Create a new Project
4. Create a new compose service
5. Try to select one of the repo with the same name in the git source of the service

Current vs. Expected behavior

It should select the one you actually select and not both + the hover is also trigered on both when the mouse is hover one of them

Provide environment information

Dokploy version v0.29.11

Which area(s) are affected? (Select all that apply)

Docker Compose

Are you deploying the applications where Dokploy is installed or on a remote server?

Same server where Dokploy is installed

Additional context

Will you send a PR to fix it?

No

[dosubot]

Hi @MatHoyer! I'm Dosu and I'm helping the Dokploy team.

This bug is caused by the repository selection logic using only repo.name as the identifier instead of a unique composite like owner/repo. There are two specific places causing the issue:

1. Double check marks — The CheckIcon visibility compares only repo.name === field.value.repo [1], so when two repos share a name across different orgs, both match and show the check.

2. Double hover highlights — The CommandItem component receives value={repo.name} [2]. Since cmdk uses this value for selection state tracking and hover styling, items with duplicate values get highlighted together.

The fix requires two changes in both SaveGiteaProvider [3] and SaveGiteaProviderCompose [4]:

1. CheckIcon comparison — check both owner and repo name:

   repo.name === field.value.repo && repo.owner.username === field.value.owner

2. CommandItem value — use a unique composite:

   <CommandItem value={`${repo.owner.username}/${repo.name}`} ...>

The form state already stores both owner and repo correctly, so only the UI comparison/display logic needs updating.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.