Follow

Complaining about Vercel not supporting Hugo's "enableGitInfo" parameter 

It's been bugging me for a while that Vercel is generating incorrect "last modified" datetimes for my wiki pages on my site. What it seems to be doing is getting the last modified date only if it's within the ten most recent commits. If the last modification was further back than that, it prints the last modified datetime of the tenth-most recent commit. From the docs it looks like Vercel is not even fetching git commit author dates (but commit SHAs and commit author logins, those it fetches…), so instead I guess it stores some cache that only goes back ten commits? I have no real clue, but because I don't know how to fix this, I've commented out the part of my template that generated "last modified" text for my wiki pages. Better to display nothing than to have it display something that's wrong for the vast majority of pages…

I mean… one way to fix this would be to build my site using GitLab's CI/CD and just upload the built files to Vercel, instead of GitLab merely passing the source files along for Vercel to build. But ugh, what a hassle to change that all around 😩 Another strategy would be to manually set a "last modified" date in the front matter of pages I want to have one, and display that in preference to whatever git says. (Or even disable enableGitInfo entirely, if it's just resulting in junk data.) That'd also be annoying, though. So, for the moment, I think just not displaying "last modified" dates'll have to be the go. (original post)

Sign in to participate in the conversation
Toot.Cat

On the internet, everyone knows you're a cat — and that's totally okay.