Ability to accept/disregard repo cleaner changes
I would like the repo cleaner to work more like the problem analyser, offering a chance to accept or disregard the suggestions before executing it.
Currently Repo Cleaner can only be enabled/disabled only at team level settings, thereby forcing the setting team-wide, which effectively rolls onto all the projects/repos using Gearset for deployments.
I have come across a situation where I would not like to alter the repo with changes any more than what I have actually changed, but since its a team-wide setting the repo cleaner was getting triggered in and bringing in more changes to my repo than what I wanted it to. The only way to get around was to disable it temporarily, finish my deployments and then re-enable repo cleaner. So, if it works similar to problem analyser, then I could have simply chosen to disregard the suggested repo cleaner changes quite easily.
Additionally, I think repo cleaner should not push its changes with my commit, it should have its own commit anyway.
Kuljit Singh Tomar
shared this idea
-
Dafydd Johns commented
As a Salesforce partner, we use gearset across a number of different clients. Given there is a bug in how a deleted field's permission to not appear at top level in a comparison (but do when you expand a profile or permission set), getting other dependencies to be delted is tricky or time consuming. Repo cleaner had been a bit problematic in the past (a bit like the problem analyzer can CAUSE problems for CI jobs), so either having a way to accept actions or to enable this on a per project level would be great.