Scott Coleman
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 An error occurred while saving the comment Scott Coleman
commented
Without this feature built into the tool, I imagine the flow would work like this:
- Do a comparison with the dev sandbox as the source and the integration sandbox as the target
- Examine the diffs for each component looking for conflicts
- Manually merge any changes we don't want to overwrite into the component in the dev sandbox outside of the tool
- Refresh the comparison in the tool (assuming the refresh action pulls the updated metadata)Scott Coleman
shared this idea
·
Kevin, I'm thinking of a team development flow where two developers work in their own development sandboxes and then use Gearset to promote their changes to an integration sandbox. If they have both made changes to the same Apex class, it would be cool for the second developer that deploys to be able to do the diff and merge right in Gearset.