TfsGitRepositoryTool

[giscus[bot]]

This discussion is for questions, feedback, and community support related to the Tfs Git Repository Tool.

Quick Reference

• Documentation: Tfs Git Repository Tool

How to Use This Discussion

• Ask Questions: If you need help configuring or using this component
• Share Examples: Post your configuration examples or use cases
• Report Issues: Describe any problems you encounter (though bugs should be reported as GitHub Issues)
• Request Features: Suggest improvements or new features

Related Documentation

Please refer to the official documentation for detailed configuration options and examples.

[wolfsacher]

not clear to me, how source and target repo should be listed in the json file...
should I replace RepoInSource by the name of the source repo or should there be two elements in json...RepoInSource and RepoInTarget with their specific values?

[MrHinsh]

@wolfsacher, its just with the name of the repo. In the sample above RepoInSource and RepoInTarget represent the text based name as it apears in the UX.

In this example the name is Azure-DevOps-Git-Tools which you can find on the URL as "https://dev.azure.com/nkdagility/_git/Azure-DevOps-Git-Tools".

You only need to add mappings if the name is diferent between the soruce and target.

[aderant-robertgray]

Is it possible to set the source and target repos via environment variables?
Would it look something like MigrationTools__CommonTools__TfsGitRepositoryTool__Mappings__SourceRepository = "TargetRepository"?

[MrHinsh]

I dont think that would work. MigrationTools__CommonTools__TfsGitRepositoryTool__Mappings is a Dictionary... so you could do:

MigrationTools__CommonTools__TfsGitRepositoryTool__Mappings[0].key = "SourceRepository"
MigrationTools__CommonTools__TfsGitRepositoryTool__Mappings[0].value = "TargetRepository"

I think.....

[MrHinsh]

Although why would you need to do that?

[aderant-robertgray]

we have a tfs server with about 15 projects all wanting to migrate to ADO and the git repos are being hosted in github. Im trying to run the tool using mostly environment variable configuration so that I dont need a hand crafted configuration.json for each project.

[MrHinsh]

The https://github.com/nkdAgility/azure-devops-automation-tools can help you automate that.

[MicE44]

Hi,
I tried this many time with version 16.1 now.
But It ignores it in the "CommonTools": area.

  "TfsGitRepositoryTool": {
    "Enabled": true,
    "Mappings": null
  },

or

 "TfsGitRepositoryTool": {
    "Enabled": true,
    "Mappings": {
      "CS-Cinematic-Anatomy": "CS-Cinematic-Anatomy"
    }
  },

or

 "TfsGitRepositoryTool": {
    "Enabled": true,
    "Mappings": {
      "https://dev.azure.com/shsds/_git/CS-Cinematic-Anatomy": "https://dev.azure.com/SHS-CS-DDO/_git/CS-Cinematic-Anatomy"
    }
  },

from
https://dev.azure.com/shsds/_git/CS-Cinematic-Anatomy
to
https://dev.azure.com/SHS-CS-DDO/_git/CS-Cinematic-Anatomy

Whats the right command?
Thanks for your feedback.

[MrHinsh]

Which part do you think is wrong, and in what way?

[MicE44]

I opend this Issue:
#2662

I cant use TfsGitRepositoryTool in my json file. The tool ignore the "enable" flag.

[MrHinsh]

Are you trying to set it to "false"? It is enabled by default, and mapps all git repos that have the same name from source to target without any additional cofiguration.

[jannecklarsson]

I have the same issue in 16.1
"CommonTools" is ignored.

"CommonTools": {
  "TfsGitRepositoryTool": {
    "Enabled": "True",
    "Mappings": null
  },

[MrHinsh]

Im not sure what you mean by "ignored". I am able to disable TfsGitRepositoryTool using CommonTools after installing v16.1.

If its ignoring it that would suggest that your config is not correct. This works for me.

{
  "MigrationTools": {
    "Version": "16.0",
    "CommonTools": {
      "TfsGitRepositoryTool": {
        "Enabled": "false"
      }
    }
  }
}