You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Author info on documentation pages is incorrect in production.
That's because it's based on the git commit log, which we parse to see who has worked on a given page/file.
However, Vercel does a shallow clone when building the site, and so this info is not available when running a build on Vercel.
There's a few things we can try to side-step the problem:
Get Vercel to do a full clone. Not sure this is even possible, or what the impact would be on build times
Build outside of Vercel (like in GitHub actions for example) and push to Vercel to publish (more stuff to maintain)
Generate this list of updates periodically (in a GitHub action perhaps) either push it to our backend or make it available elsewhere so we can pull it in during the build step
The latter option has the benefit that it will fix the problem without slowing down the build (actually, it will make it faster).
We could have a pipeline that only runs when merging to the develop branch for this.
What seems to be the problem? 馃
The Author info on documentation pages is incorrect in production.
That's because it's based on the git commit log, which we parse to see who has worked on a given page/file.
However, Vercel does a shallow clone when building the site, and so this info is not available when running a build on Vercel.
There's a few things we can try to side-step the problem:
The latter option has the benefit that it will fix the problem without slowing down the build (actually, it will make it faster).
We could have a pipeline that only runs when merging to the develop branch for this.
Design / Plugin / Package 馃
No response
Additional context
Example of incorrect data: https://freesewing.org/docs/designs/bibi/notes
(was written by @HaasJona but says @joostdecock becuase that's the fallback default it seems).
The text was updated successfully, but these errors were encountered: