GitRepositoryEnricher: Target Repo not found. Cannot map

[Catalin1F]

Hi Team,
After the migration is done I have noticed that the links to Commits are not working : “Commit not found or no permission to access it.”
I have added the same commit manually for one of the migrated workitems using “Add link” from ADO and it allowed me to add, so the Git repo was migrated with success and I have the right level of access .

This is what I see in the logs :

[04:49:32 INF] GitRepositoryEnricher: Enriching 152779 To fix Git Repo Links
[04:49:32 WRN] GitRepositoryEnricher: Target Repo not found. Cannot map https://kt@dev.azure.com/kt/TPM/_git/Tpm to ???
[04:49:32 WRN] GitRepositoryEnricher: Target Repo not found. Cannot map https://kt@dev.azure.com/kt/TPM/_git/Tpm to ???
[04:49:32 WRN] GitRepositoryEnricher: Target Repo not found. Cannot map https://kt@dev.azure.com/kt/TPM/_git/Tpm to ???
[04:49:32 WRN] GitRepositoryEnricher: Target Repo not found. Cannot map https://kt@dev.azure.com/kt/TPM/_git/Tpm to ???
[04:49:32 DBG] GitRepositoryEnricher: Saving 152779
[04:49:32 DBG] TfsExtensions::SaveToAzureDevOps

Could you please advice what could be a possible root cause?

[MrHinsh]

If the git repos do not have the same name you will need to add a mapping for the changes.

[Catalin1F]

Thanks @MrHinsh !
Not sure if the name of the Git Repo is case sensitive for ADO. I have noticed today that the source repo has just uppeercases while the target one some lowercases.
I am mapping uppeercase with lowercase to see the impact :)

[MrHinsh]

I'm pretty sure that we use a dictionary that is case insensitive. Its worth a try through.

[Catalin1F]

yes, it is case sensitive. So "KT" is not the same as "Kt" and I had to rename the Repo and forced
the work items to sync again ( "FilterWorkItemsThatAlreadyExistInTarget": false,) and now it works :)