在 TFS 中的不同项目下创建一个项目及其父项目的分支
我有以下结构：
$/ProjectA [使用 MS Agile 模板]
--Branch1
$/ProjectB [使用自定义敏捷模板]
--[待创建分支]
如何在ProjectB中创建与$/ProjectA/Branch1有父关系的新分支？
我们的要求是我们不能在同一个项目下，因为我们必须使用不同的模板，但我们仍然希望将新项目中的代码合并回项目A。当您创建一个新项目时，我检查了 TFS 中的选项，该项目允许您使用现有的源代码管理，但问题是：
1.没有选项可以在项目中引入特定分支[全部或全部]
2.I由于某种原因无法重命名新项目中的新分支
我知道这可以通过在这两个项目之间使用无基础合并来实现，但我想知道是否仍然有办法在不同的这两个分支之间进行平滑合并项目。
PS：我们使用的是 VS 2010 和 TFS 2010
I have the following structure:
$/ProjectA [Uses MS Agile Template]
--Branch1
$/ProjectB [Uses Custom Agile Template]
--[To Be Created Branch]
How can I create this new branch in ProjectB that has a parent relation with $/ProjectA/Branch1?
Our requirement says that we cannot be under the same Project because we must use different templates, but we still want to merge the code from new project back to the ProjectA. I checked the option in TFS when you create a new Project that lets you use an existing source control, but problem with that is:
1.There is NO option to bring in specific branches in a Project [Its all or none]
2.I cannot rename that new branch in the new project for some reason
I understand this can be achieved by using a Baseless merge between these 2 projects but I would like to know if there is still a way to have a smooth merge between these 2 branches in different projects.
P.S: we are using VS 2010 with TFS 2010
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
从一个团队项目分支到另一个团队项目应该不会有任何问题。您应该能够像处理任何分支一样执行此操作：只需选择
$/ProjectA/Branch1，选择 Branch，然后输入$/ProjectB/ToBeCreatedBranch的分支目标路径>。这是因为实际上，团队项目在 TFS 版本控制中的范围相当有限 - 它主要将源代码控制树视为从
$/开始的大层次结构，并且团队项目并不是特别特殊，除了一些非常专业的操作。 （签入策略由团队项目查询，锁定级别和标签的设置也仅限于团队项目。）我有点不清楚您在创建新团队项目时指定的版本控制选项 - 您应该只为其创建一个新的源树节点，然后您可以在
$/ProjectB下创建项目分支。There's shouldn't be any problems in just branching from one team project into another. You should be able to do this just like you would any branch: just select
$/ProjectA/Branch1, select Branch, and enter a branch target path of$/ProjectB/ToBeCreatedBranch.This is because realistically, Team Projects are of fairly limited scope in TFS version control - it primarily treats the source control tree as a big hierarchy beginning at
$/, and team projects are not particularly special, except for some very specialized operations. (Check-in policies are queried for by Team Project, as are settings for locklevels and labels are scoped to Team Projects.)I'm a little unclear what version control options you specified when you created the new Team Project - you should have just created a new source tree node for it and then you can create your project branches beneath
$/ProjectB.