Compare to a Specified Source Control Folder vs. Root of Source Control Repository during Comparisons.
I would like the ability to specify a file folder when comparing a sandbox to version control. Most of my salesforce projects have a SRC folder with the contents of my package.xml. By not allowing a source folder when selecting the branch to compare, it renders this comparison useless as all files show as new. Please implement this feature to allow a directory for comparison so that I can justify using / selling this tool.
Ben Faber
shared this idea
Hi Ben,
I’m glad that the issue was resolved for you with the adjustment in the location of the package.xml.
Regards,
Stephen
-
Hi Ben, thanks for the suggestion. To clarify Gearset's current behaviour (since it isn't that obvious): Gearset will treat the "src" folder as the root of a comparison but this folder must contain your "package.xml" file.
If your "package.xml" is in a parent directory (or somewhere else), you can move it into your "src" folder and get the behaviour you described.
If you have any issues with getting this to work (or if I've misunderstood your suggestion), feel free to email team@gearset.com or use the in-app chat widget :)
-
Ben Faber
commented
I think you guys really should allow an extra option to point to the folder directory of your source control repository along with the branch. So I should be able to say during comparison, Compare Sandbox A -> Bitbucket (Branch A) at folder <root>/src. by not supplying this option I think will limit the ability to sell the tool for the client I'm working with. Any github or any public repository always has ways to deal with separation of salesforce metadata source code vs. non-metadata source. One particular example are compressed resource bundles....a lot of IDE's have specific similar ways to handle resource bundles where you can source control a resource bundle unzipped in repo/resource-bundles/ format, and the compressed format is repo/src/StaticResources.