Gearset has introduced a feature that allows users to exclude unlocked packages from the comparisons run via Compare and deploy as well as from any custom metadata filters, including metadata filters for CI jobs.
Default configuration
In comparisons within Gearset, all metadata that can be detected as part of an unlocked package is included by default.
However, we understand that sometimes you may want to exclude unlocked package metadata from your comparison.
Within the packaging sidebar on the right hand side of the filter, there is the option to Exclude unlocked packages from your comparison.
In brackets we're showing the number of distinct unlocked packages identified across the two environments.
On the below example, we've amended the default behaviour and excluded unlocked packages from the filter (by enabling the toggle):
This setting can be amended for existing metadata filters, including filters created before Gearset made this feature available.
Expected behaviour when retrieving unlocked package metadata
An item that is a part of an unlocked package in one of the compared environments but is not in the other will always be retrieved and shown in Gearset's comparison results.
This applies even when option Exclude unlocked packages is enabled.
Limitations
Currently, there isn't a way within Gearset to filter out only specific unlocked packages.
This setting in our app cannot filter out specific packages - to achieve this you must exclude all from your comparison.
Feedback
If you have a use case that is not covered here, we’d love to hear your feedback!