-
We recently migrated from TFS to a new Git-based organization. After moving several repositories to Git, we decided to migrate the work items as well. I used a tool to transfer the work items, and the process went smoothly. However, since the old version control system was TFS and the new one is Git, I'm now facing an issue with migrating changesets. Ideally, I'd prefer not to move the changesets but instead keep them as links to the old organization. Currently, the changesets are transferred as links, but these links point to the new organization. Since the changesets themselves weren't moved, clicking on the links results in a "Not Found" page. Could you provide advice on how to handle the changesets in this scenario? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
When you say When you converted your repos from TFVC to Git you would have used Git-TFS. This tool outputs a mapping file from Changeset to Commit that you can use as input into this tool to mapp these items. Without that file there is no way to map them. |
Beta Was this translation helpful? Give feedback.
When you say
TFS
I think that you meanTFVC
(Team Foundation Version Control)...TFS
supports bothTFVC
andGit
source repos.When you converted your repos from TFVC to Git you would have used Git-TFS. This tool outputs a mapping file from Changeset to Commit that you can use as input into this tool to mapp these items. Without that file there is no way to map them.