Use GitRepoMapping to fix commit / PR links from repos in different projects?

[raph91]

Hi

Currently I am trying to migrate work items (TFS/Azure DevOps Server to Azure DevOps Services) that have related links to commits and pull requests from repos outside the project (in the same collection/organization).

The links to commits from the git repo within the same project are resolved, but the ones pointing to a git repo within a different project (with the same source/target name though) are still missing.

I get the following errors when I run the migration tool:
[16:16:53 INF] GitRepositoryEnricher: Enriching 20 To fix Git Repo Links
[16:16:53 WRN] GitRepositoryEnricher: Could not find source git repo - repo referenced: null/null
[16:16:53 WRN] GitRepositoryEnricher: Could not find source git repo - repo referenced: projectA/repoA
[16:16:53 WRN] GitRepositoryEnricher: Could not find source git repo - repo referenced: projectA/repoA
[16:16:53 WRN] GitRepositoryEnricher: Could not find source git repo - repo referenced: projectB/repoB

I don't fully understand why it can't map the ones from projectA/repoA as I already migrated the git repo and the source and target name are the same.
My user is a project collection administrator in both systems.

Any idea?

BR

[raph91]

I figured it out, I had to add source repo and target repo to the GitRepoMapping, altough they still have the same name:
"GitRepoMapping": {
"repoA": "repoA",
"repoB": "repoB",
},

[MrHinsh]

This is needed because the link uses the project GUID (ID) and not the name in the URL. The tool looks up the git-repo name and then uses the project it is contained in. Good catch!

[NormanGarciaV]

Hi @raph91, @MrHinsh
I am having the same problem, for the mapping, when you say "repoA": "repoB", you use the full URL of the repo?

Thanks.

[MrHinsh]

Just the name is required.

[NormanGarciaV]

Thanks.. will try that.

[jibdev97]

This fixed my issue converting the commit links as well! Thank you!