Support package.xml filtering when using Git comparison with a SFDX folder structure
When using a git repo with a SFDX folder structure + package/xml (in the /manifest folder) gearset dos not take into account elements in the package.xml when checking the option (filter with package.xml)
Anonymous
shared this idea
-
Ivan
commented
Using SF Project with the SFDX Folder Structure, definitely needed feature to work with the package.xml!
-
Mahesh Gujjala
commented
We use SFDX folder structure. This feature is urgently needed!, Thanks!!
-
Richard Wang commented
This is definitely needed!!!
-
Dave Hamburg commented
Need this so much!
-
tracie
commented
Yes! extremely needed ---- I would like it even better if we could deploy specific changes from a repo and not the entire repo. :)
-
Anonymous
commented
This is necessary, please implement.
-
Jan Julian
commented
This is going to be the new default setup for org development as it's documented by SFDC: https://forcedotcom.github.io/salesforcedx-vscode/articles/user-guide/org-development-model
-
Noel Austin
commented
We use SFDX folder structure. This feature is urgently needed!
-
Gleb Urobushkin
commented
This reciprocal feature is really needed. Its lack can cause serious deployment issues and confusion in Gearset installations that integrate with customer git repositories.
Moreover, it seems Gearset will benefit greatly from the architecture standpoint and improved adoption all due to the true support of SFDX and general CI practices, -
John Ellison
commented
As more of us are moving to the SFDX structure, this is something that would be very beneficial and for my team would help with our CI/CD process we want to implement.