docs: clarify metadata.timestamp uses git commit date#6188
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
ethanpalm
approved these changes
Jun 16, 2026
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Clarify that the "Last modified on [date]" timestamp shown when
metadata.timestampis enabled reflects the source file's last git commit date for GitHub/GitLab-backed deployments, with a fallback to the deployment timestamp.Changes
organize/pages.mdxto describe the git commit date behavior and fallback.metadata.timestampentry inorganize/settings-reference.mdxwith the same clarification.zh,es, andfrlocales.Context
Source PRs:
Note
Low Risk
Documentation-only edits with no runtime, config schema, or behavior changes in this repo.
Overview
Documents how the “Last modified” date is chosen when
metadata.timestampis enabled.The Last modified timestamp section in
organize/pages.mdxnow states that on GitHub/GitLab-backed deployments the shown date comes from the last git commit that changed the page source file, and otherwise falls back to the most recent deployment timestamp.The
metadata.timestampentry inorganize/settings-reference.mdxcarries the same wording. Equivalent updates were applied in the es, fr, and zh locales for both files.Reviewed by Cursor Bugbot for commit 9ee8b07. Bugbot is set up for automated code reviews on this repo. Configure here.