fix static builds lacking git info

[geekosaur]

Please read Github PR Conventions and then fill in one of these two templates.

---

Template B: This PR does not modify behaviour or interface

E.g. the PR only touches documentation or tests, does refactorings, etc.

Include the following checklist in your PR:

• Patches conform to the coding conventions.
• Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

[ulysses4ever]

In the interest of experimenting, this could be fast-tracked, I hope.

[ulysses4ever]

If it's "ready for review", maybe un-draft it too?

[geekosaur]

Haven't yet modified the git stuff to degrade gracefully on lack of git info yet; been focused on trying to make the Alpine job provide it.

[ulysses4ever]

All right, it's up to you, of course. In my mind, these were separate issues. But I guess it may be more ergonomic to kill two birds with one PR!

[ulysses4ever]

@Mikolaj @Kleidukos @ffaf1 can we get one more review here, please? I think everyone loves cabal-head. Let's make it even greater again with git info working for static builds!

[Kleidukos]

@geekosaur I believe you can merge this PR!

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.

If you want to requeue this pull request, you need to post a comment with the text: @mergifyio requeue

[ulysses4ever]

I can confirm that the fresh static cabal-head has the Git info now! Thanks a ton @geekosaur!