Update docs/en/reference/default-theme-last-updated.md

pull/4780/head
Divyansh Singh 3 months ago committed by GitHub
parent d727d5c580
commit 9b4dc0401f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

@ -3,7 +3,26 @@
The update time of the last content will be displayed in the lower right corner of the page. To enable it, add `lastUpdated` options to your config.
::: tip
To display the last updated time, at least one Git commit is required, as we retrieve the most recent Git commit timestamp by default. Additionally, if all file update times consistently match the latest project commit (rather than reflecting actual file modifications), please verify whether your file history is incomplete (e.g., due to using Git's shallow clone mode).
VitePress displays the "last updated" time using the timestamp of the most recent Git commit for each file. To enable this, the Markdown file must be committed to Git.
Internally, VitePress runs `git log -1 --pretty="%ai"` on each file to retrieve its timestamp. If all pages show the same update time, it's likely due to shallow cloning (common in CI environments), which limits Git history.
To fix this in **GitHub Actions**, use the following in your workflow:
```yaml{4}
- name: Checkout
uses: actions/checkout@v4
with:
fetch-depth: 0
```
Other CI/CD platforms have similar settings.
If such options aren't available, you can prepend the `docs:build` command in your `package.json` with a manual fetch:
```json
"docs:build": "git fetch --unshallow && vitepress build docs"
```
:::
## Site-Level Config

Loading…
Cancel
Save