This message was deleted.

That is not possible. The configuration phase is required (it's basically evaluating your build scripts, Gradle plugin code and setting up dependencies for all tasks). Without a configuration phase, Gradle would not be able to know that your task exists. The configuration phase should not take too long, but it might certainly multiply the time spent if you're executing some git commands. If it's meant for interactive usage, and doesn't need any input from the Gradle model, I personally would go with a shell script instead

You should make sure that you properly leverage task-configuration avoidance though. If you break, you cause all tasks to be configured, which can then require significant time. If you properly adhere to it, only the tasks that are going to be executed are configured.

You can also use the configuration cache to avoid running the configuration phase multiple times.