🔧 Preserve accurate last-update attribution

[JFWooten4]

Why

Docusaurus derives each page's last-update author and timestamp from Git history. The production workflow currently checks out only the triggering commit, so that shallow clone's root commit can be attributed to pages it did not modify.

For example, the deployed SDEX page reports a September 2 update by maz, while the latest commit that actually changed the page is 7a80e82bd from July 15 by John Wooten.

What changed

Fetch the complete repository history in the production build-and-push workflow by setting fetch-depth: 0 on the checkout step. This gives Docusaurus the history it needs without changing page content.

Verification

corepack pnpm build completed successfully with full history. The generated SDEX page rendered:

Last updated on Jul 15, 2026 by John Wooten

[Copilot]

Pull request overview

Updates the production workflow so Docusaurus can derive accurate page-update attribution from complete Git history.

Changes:

• Configures checkout with fetch-depth: 0.
• Documents why full history is required.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[ElliotFriend]

that's a pretty good catch, there! let me get our ops team to review, just to double-check there isn't any build performance considerations.

thanks!!

[satyamz]

@ElliotFriend This will increase build time by couple of seconds and size of the docker image but I do not think this will have any impact in the production since as I understand we just copy build/ directory in the final image.