Allow user to choose the folder in a git repo that contains metadata
Improve git access by allowing the user to define folder where metadata is stored in a git repo.
We are not keeping directly content of src in git branch but src folder because we have there also few other folders.
The problem is that if I try to compare sandbox with git then I am getting results that all files are new.
Pawel Wozniak
shared this idea
That’s great!
I’m glad that the issue was resolved for you with the adjustment in the location of the package.xml.
Regards,
Stephen
-
Ben Faber
commented
Ok great. This looks a lot better. We had the package in a git ignore and was being copied from a different build system based on what was being deployed, so it wasn't picking up the differences. I am now past this issue and understand how this works.
-
Hi Pawel, 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 just created a similar feature request here https://gearset.uservoice.com/forums/283474-help-us-improve-gearset/suggestions/18615979-allow-user-to-choose-the-folder-in-a-git-repo-that. I'm surprised the tool is not doing this over a year later. My bitbucket repository has a structure like so.
root/src, it detects the package.xml, but when comparing with a sandbox, all files show as new. Was this the similar experience you had? -
jenkins
commented
Our GitHub is a root folder that contains an SRC folder that contains all my code. Is yours not doing this?