This analyzer helper resolve issues where an object's name changes case.
What triggers this problem analyzer?
An object with the same name in a different case on the source and the target will trigger this analyzer.
What problem is it solving?
Imagine if we named an object VEhicle (adding an uppercase E by mistake). After deployment, we change the object in Salesforce to set the label and the object name to Vehicle.
Gearset will show us the change in the object name:
Deploying to Salesforce
In theory, Salesforce metadata is case-insensitive, but that is not always enforced. Deploying a case difference may cause the deployment to fail.
Deploying to git
If the target of your deployment is a git repository, deploying changes to file casing you can lead to multiple versions of the same component being added to your repository, which can be confusing and hard to manage.
How does it work?
Gearset will rename objects in the deployment package to use the target case. This will make the deployment more likely to succeed and make managing git repositories easier.
You can opt not to accept the suggestions made by the analyzer if you wish to deploy the case change.