Deploying feature branches of your Salesforce metadata
Stephen Chambers on April 18th 2016
Our support for GitLab and GitHub has provided flexibility for people to use their existing source control solutions to compare and easily migrate Salesforce metadata changes.
There has been one additional feature that's been missing from our initial support of the source control story, and that's been providing the ability to compare Salesforce metadata from a specific branch within a repository, often implemented when using a feature Branch flow.
The good news - branch support is now available for GitHub and GitLab, and it's very easy to get started.
Using source control in Gearset to compare Salesforce metadata
Step 1: Connect to a GitHub or GitLab accountIf you're new to Gearset and want to use either GitHub or GitLab to compare your metadata, the very first step is to connect your account(s).
Simply visit the 'Manage linked services' section from within the manage orgs tab and connect to either git service, complete the account authorization process and you're all good to go!
Step 2: Choosing the branch to compare your Salesforce metadata againstWhen configuring a comparison, simply pick the source control option, pick the account you want to use and finally the repository and branch you're looking for.
The only thing left to do is specify the target organization and you can begin comparing the metadata between your source controlled metadata and Salesforce org in preparation for deploying your latest metadata changes.
For those of you who use BitBucket as their Git solution - we haven't forgotten about you. We'll also be adding support for BitBucket in Q2 of this year and get in contact using our UserVoice forum if you think we should do this faster!
As always, we love getting feedback or questions about what we're doing. If you'd like to get in touch with us, just drop an email to [email protected] and we'll be happy to help.