Rething short SHA handling with an eye on determenistic builds

[alerque]

This has become a little bit of a sore point for me working on Fontship. I'm keeping an eye on reproducible builds for fonts as a long term goal and one thing that changes on me is how long the SHA is. This is a moving target because ⓐ upstream Git keeps changing their defaults and ⓑ global user configs can change this. My local system is generating 8 character short SHAs, remote CI is giving me 7.

I'd like to either be able to specify the SHA myself (I have the information already, I could pass it to font-v and save it the trouble of looking it up) or at least a way to specify it manually. Currently the only workaround I can think of is to fiddle with the local working directory's Git config before running font-v which kind of feels aggressive to me.

See #2 for discussion of current handling.

[chrissimpkins]

I'd like to either be able to specify the SHA myself

You can write the full version string programmatically with the font-v library (and without font-v automation of the git part of it).

https://github.com/source-foundry/font-v#set-entire-version-string-with-associated-metadata

Does that approach work?

I am open to changing the behavior here. We could use the full SHA string rather than an abbreviated short SHA or abandon this approach altogether.