Anonymous
My feedback
1 result found
-
82 votes
Merging differences between Apex classes and VisualForce pages is difficult to do automatically due to the understanding required by the developer. For differences between two orgs in other object types, Gearset helps you sidestep that with our granular comparison results. This blog post explains more: https://gearset.com/blog/merging-salesforce-metadata
An error occurred while saving the comment Anonymous supported this idea ·
One of the advantages of working with Metadata rather than built in change sets is the ability to intelligently decide which lines we want to move forward, rather than to clobber entire files and/or contain unimportant or even undesirable artefacts of the development process which should only live and die in the development sandbox.
Without merge tools, using Gearset to modify our git repository has been making the repository somewhat dirty.
Also, as/if/when my solving problems outpaces my manager who thoroughly reviews my code, I'm finding work done in Sandbox A becomes incompatible with Sandbox B, requiring me to perform merges on my own machine rather than in Gearset.