sbrassard Posted December 12, 2014 Report Share Posted December 12, 2014 Can someone please explain to me the significance of a Top Level Branch and why they are an option, or how some development shops use them? The only thing that comes to mind is by creating a top level branch called "/Releases" and then placing all prisitine, code complete, QA passed releases that is currently deployed in a production environment... I mean, that's only one example, but is that a correct way to think of them as? Also, are there any drawbacks to using them in a repository? Thanks Link to comment Share on other sites More sharing options...
manu Posted December 15, 2014 Report Share Posted December 15, 2014 Hi! it's just a naming issue, a top level branch has no prefix. A child branch has always a prefix... /main/task001 or /MyTopLevelBranch/task002. In terms of SCM a top level branch and a child branch is the same thing, both start from a base changeset. No drawbacks there. Top level branches are usually created when we need cleaner branch names. Your QA scenario is also a good example where top-level branches can be used. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.