Fix time-stamping to work with GPG signed commits

[shinnok]

If HEAD is pointing to a gpg-signed commit, the result of the previous GET_CURRENT_COMMIT_TIMESTAMP expression will include GPG info, which in turn will end up in .update.timestamp for the current project. This is especially relevant if the user has configured git config log.showSignature true.

Fix this behavior by ignoring irrelevant GPG signed status with --no-show-signature.

[arnetheduck]

this would bump git version req to ... 2.10 I think - is there another way to avoid it (ie sed?)

[shinnok]

Given my specific output scenario:

$ git log --pretty=format:%cd -n 1 --date=unix
gpg: Signature made Tue Aug  8 10:16:42 2023 EEST
gpg:                using RSA key DC57D8288951F46
gpg: Good signature from "Teodor <redacted>" [ultimate]
1691479002

Assuming that GPG output will always start with gpg: for everyone, we can gpg -v or sed it out. However, I would actually tail -n1 to get the timestamp out, do you think this is a better assumption? That the timestamp has a better chance to end up on the last line, than otherwise.

[shinnok]

@arnetheduck Hi, what do you think of just grabbing the last line with tail, should I just push a change with just that, for the time being?

[arnetheduck]

Hi, what do you think of just grabbing the last line with tail, should I just push a change with just that, for the time being?

I think that it's an excellent idea provided you test it with some git versions that ship with non-obsolete LTS releases of debian / ubuntu / redhat.