Notifications
Announcements
No record found.
Hi,
Currently I configure Metadata and Projects as branches, and Dev as a folder.
Can I also convert the Dev folder to Branch as well? Is there any negative impact if I make such change?
Thanks,
Dev should be a branch, Metadata and projects should be folders in the branch. About your question, I think the quickest way to find an answer to "can I?" questions is to try it.
Yuji ,
You have created another thread similar to this in the past.
community.dynamics.com/.../967628
See my reply on the above thread
-----------------------------------------------------------------------------------------------------------------------------
Structure looks correct . Dev and main are going to be your branches and metadata and projects are going to be inside those branches as folders.
docs.microsoft.com/.../version-control-metadata-navigation
you can refer to some best practices documentation about creating dev and release branches. Ensure that you don't create so many branches that you need to spend too much time in merging the changes.
docs.microsoft.com/.../new-environments-visual-studio-teams-branch-retail-projects
docs.microsoft.com/.../aa730834(v=vs.80)
Since I have created MetatData and Projects as branch, if I convert Dev as branch, will this change impact the my daily development?
Take a back up of your branch and try it .
And is it still okay to keep MetaData and Projects as branches, so Dev branch contain another two branches?
Hi Yuji,
You cannot nest branches; that means, you cannot convert a folder (DEV) to a branch if it either contains a branch (metadata and Projects) or is contained by a branch.
As sukrut suggested above, take a backup of your metadata and Projects branch and then convert these branches to folders.
Once they are folders, then you can convert parent folder DEV to a branch.
refer https://docs.microsoft.com/en-us/azure/devops/repos/tfvc/branch-folders-files?view=azure-devops
Hello Yuji,
There is no negative impact on converting a Dev folder to a branch.
Looks like there are various phases in the project or tasks that you are involved in. If yes, then agree with the approach that you are taking. Better to create one duplicate branch that hosts the previous phase code.
Thanks,Navneeth Nagrajan | Dynamics 365 Technical Consultant
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
André Arnaud de Cal... 456 Super User 2025 Season 2
Martin Dráb 429 Most Valuable Professional
BillurSamdancioglu 239 Most Valuable Professional