Exactly, gradle is so slow that I ditch it into the ground. Just starting a blank project is so a bad experience. Nothing beat maven and a couple of shell script.
I am convinced if they hadn't got Google's sponsorship, when Android decided to move into Gradle during Eclipse to InteliJ migration, we would be talking about Gradle as much as Grails is still discussed at local JUGs.
I did look at modifying the merge commit message, but I couldn't figure out how to accurately detect a merge commit.
Having re-looked, I just found 'git rev-parse --verify MERGE_HEAD' which may help here. Time to do some testing. It would be good to clean up and standardise the commit msg itself too. Thanks.
The prepare-commit-msg hook is the one. One of the hook args is the type of commit (merge, squash, etc). And the merge commit msg files exist (SQUASH_MSG, MERGE_MSG) so my original logic all works.
$ git log -1
commit 735ce5f9998736c4066d63ab851df2023640dad5 (HEAD -> master)
Author: Doug Bridgens <thisdougb@users.noreply.github.com>
Date: Tue Apr 1 22:31:22 2025 +0100
test4 does some stuff
Time spent on feat_test4: 0d:0h:7m secs=426
It’s a sql that compiles to the real database sql based on configuration.