Suppress irrelevant Suggested Fixes when deploying to git
The problem analysis comes up with a number of Suggested Fixes which may make sense for improving Salesforce deployments, but which are unproductive when applied to git deployments.
For example, the suggestion to remove TASK.WHAT_NAME, or to omit Standard Objects, will only serve to create a git repo which is an inaccurate reflection of the source org. Each time we deploy to that git repo, we will continue to have the same changes to select or omit, since the repo is missing objects and fields from the source org.
When the deployment target is a git repo, all suggested fixes which remove fields and metadata in accordance with Salesforce best practices should be hidden/suppressed/omitted. Suggested fixes which add necessary dependencies to the deployment should still be displayed.
Jeremy Rohrer commented
I think "all" may be overstatement, but I definitely support the idea of reviewing and trimming notifications that are non-pertinent when capturing to version control.