So, my colleague Scott Moyse and I have been messing around with Branching and Merging, and trying to understand it. I was hoping to use it for a workflow at my Fusion 360 Meetup this week. Unless we are doing something wrong, it seems extremely limited.
Picture this:
Well it doesn't. Each merge shows a conflict, and overwrites the design that was merged from the other branch.
If we use the source code analogy, adding files to a project in a branch will be added to another branch when merged to it. If a merge results in a conflict for a file, then (in git anyway) you get a merge conflict that you can resolve by picking and choosing which bits of each version of the file you want.
I think it needs to work the same way for Fusion. If components (code files) have been added to a design (code project), then the merge should just add them, or at least give you the option to choose. So multiple branches merging into one branch should add all the components from each branch if they are unique.
That was really difficult to explain, so I hope it makes sense to somebody...
Gavin Bath
MFG / CAM Technical Specialist
Design and Motion Blog
Facebook | Twitter | LinkedIn | YouTube
Hi Gavin,
This makes perfect sense. You are describing a scenario of merging an assembly at a component level. The preview doesn't support this yet and it is a future item.
We definitely see a lot of value in this workflow but its a hard problem to solve, especially getting the timeline squared away after the merge. We are on it but its not something that will be supported soon.
Thanks,
Bankim