Avoid check of the ratchetFrom branch when Spotless not invoked

Currently, Spotless (Gradle Plugin) performs a check for the presence of the ratchetFrom branch on every command execution. This includes instances where Spotless-specific commands aren't called, which can lead to unnecessary checks, and adds the workaround (e.g. git fetch depth:0) for all cases.

Could we refine the ratchetFrom functionality so that it checks for branch presence only when a Spotless command is actually invoked?

I believe this adjustment could be beneficial for users who integrate Spotless into their development workflows, ensuring that the tool remains as efficient and unobtrusive as possible.

Comienza rastreando el manejo de ratchetFrom en el Spotless Gradle Plugin y cómo se invocan los comandos específicos de Spotless. Confirma que la comprobación de la presencia de la rama solo se realiza cuando se ejecuta un comando de Spotless, mientras que los comandos ordinarios de Gradle evitan esa comprobación y la solución alternativa de fetch-depth resultante.

Escrito por el modelo de indexación a partir del texto del issue.