B would be my answer. The git-tfs tool is used for migrating TFSC to Git (within Azure Devops). But in this case we need to "Migrate all the source code from TFS1 to GitHub." And Github is another product (using git as version control system). To migratie tfsc to Github, your best option would be the GitHub Importer.
"About GitHub Importer - If you have source code in Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository, you can move it to GitHub using GitHub Importer."
https://docs.microsoft.com/en-us/devops/develop/git/migrate-from-tfvc-to-git
https://docs.github.com/en/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer
"Woodgrove Bank plans to implement", "Migrate all the source code from TFS1 to GitHub."
"Tip: GitHub Importer is not suitable for all imports. For example, if your existing code is hosted on a private network, our tool won't be able to access it. In these cases, we recommend importing using the command line for Git repositories or an external source code migration tool for projects imported from other version control systems."
Why do you think that tfs1 is not private?
Both B & D are valid. Just to point out, the passage quoted by warchoon is talking about the source repo. The destination is a "private GitHub Repo". That could be a repo set to "private" visibility on GitHub.com or one on a private network via GitHub Enterprise Server. The GitHub importer tool imports to GitHub.com only.
The case study talks about the central office being in the UK, but it doesnt talk about how this data was stored prior. Was it on prem? The case study doesnt specify, but its kind of important. If you want to infer that the central UK office housed the repo servers prior, then GitHub Importer wouldnt work unless the code was given a public address, so you'd choose git-tfs. But since it didnt specify, you might want to keep it simple, and assume its publicly available because it doesnt say otherwise, in which case, GitHub Importer would work
Very good reasoning.. Both option B and D seems valid. I would opt for Git-tfs simply because this is explicitly mentioned in the doc article 'Import and migrate repositories from TFVC to Git'
https://learn.microsoft.com/en-us/azure/devops/repos/git/import-from-tfvc?view=azure-devops#advanced-migrations
Answer is D.
Git hub importer does not support importing directly from TFS. Git hub importer works only with other GIT repos.
https://docs.github.com/en/migrations/importing-source-code/using-github-importer/about-github-importer.
To use GitHub importer you need first convert your TFS repo to a git repo by using the git-tfs tool.
https://docs.github.com/en/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-team-foundation-version-control-repository
A. git clone: While you can clone a repository, this approach doesn't migrate it into Azure DevOps. It only creates a local copy on your machine.
B. GitHub Importer: This tool is for migrating repositories from GitHub into GitHub, not for migrating to Azure DevOps.
D. git-tfs: This tool is used to migrate Team Foundation Server (TFS) repositories into Git, not for GitHub to Azure DevOps migrations.
Answer is D gt-tfs
When to Use GitHub Importer vs. Git-TFS?
1. Use GitHub Importer for simpler migrations from Git-based systems (e.g., Bitbucket, GitLab).
2. Use Git-TFS if you are migrating from TFS or need more control over the migration, such as incremental migration or handling large repositories.
C - Migrating with Azure Repos (recommended)
https://docs.github.com/en/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-team-foundation-version-control-repository
I choose D until I find a good justification of C. I will not choose B because GitHub Importer requires public internet access to the code which we can't assume is the case and most likely not.
B is the answer.
https://docs.github.com/en/migrations/importing-source-code/using-github-importer/about-github-importer
If your source code is stored on a code hosting service using Git, Subversion, Mercurial, or Team Foundation Version Control (TFVC) and is accessible from the public internet, you can move the code to GitHub using GitHub Importer.
The Git-TFS tool is a two-way bridge between Team Foundation Version Control and Git, and you can use it to perform a migration. Git-TFS is appropriate for a migration with full history, more than the 180 days that the Import tool supports.
D - git-tfs
Read the official docs, guys. GitHub recommends using git-tfs, not GitHub Importer.
Source code migration > Importing from TFVC:
"We recommend git-tfs for moving changes between TFVC and Git."
https://docs.github.com/en/migrations/importing-source-code/using-the-command-line-to-import-source-code/source-code-migration-tools#importing-from-tfvc
I'll take B
https://docs.github.com/en/get-started/importing-your-projects-to-github/importing-source-code-to-github/about-github-importer
"GitHub Importer is a tool that quickly imports source code repositories, including commits and revision history, to GitHub for you."
When you go to "Code Migration tools" page within the same documentation you will see that while migrating from TVFC they also recommend git-tfs, So I will choose D option:
https://docs.github.com/en/get-started/importing-your-projects-to-github/importing-source-code-to-github/source-code-migration-tools
The content under mentioned link is changed. GitHub Importer is recommended
"We recommend using GitHub Importer to import projects from Subversion, Mercurial, Team Foundation Version Control (TFVC), or another Git repository. You can also use these external tools to convert your project to Git."
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
pdk88
Highly Voted 2 years, 6 months agowarchoon
2 years, 1 month agomfawew223
1 year, 3 months agoNian
1 year, 2 months agobasw77
Highly Voted 2 years, 8 months agobillycat
Most Recent 3 days, 2 hours agodddddddddddww12
2 months, 2 weeks agoGooldmember
4 months ago4bd3116
10 months, 1 week agovsvaid
1 year, 2 months agolematjas
1 year, 3 months agonakedsun
1 year, 4 months agoyana_b
1 year, 5 months agohalfway
1 year, 6 months agoieboaix
1 year, 7 months agozellck
1 year, 9 months agoSrirupam
1 year, 10 months agoaut0pil0t
1 year, 11 months agoarmvch
2 years agosyu31svc
2 years, 7 months agoMiniLa92
2 years, 6 months agobiglebowski
2 years, 2 months ago