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
Primary uses cases:
1. Reduce deployment churn in repositories that hold a docsite in
addition to source code. These repositories currently regenerate
and find "changed" files to deploy on every commit, even when
nothing in the Jekyll site was changed. The only artefact changing
each time is `feed.xml`.
For example: https://github.com/qunitjs/qunit/commits/gh-pages
2. Improve reproducibility of the build, as highlighted via
jekyll/jekyll#7187. By offering a choice
that simply eliminates use of current time entirely, we do not
even have to worry about mocking it.
Copy file name to clipboardExpand all lines: README.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,6 +45,17 @@ feed:
45
45
46
46
To note, you shouldn't have to do this unless you already have a feed you're using, and you can't or wish not to redirect existing subscribers.
47
47
48
+
### Updated timestamp
49
+
50
+
By default, the feed will set `<updated>` to the current time at build time, as provided by Jekyll via `site.time`.
51
+
52
+
Enable the `updated: latest_post` setting to use a deterministic value based on when the latest post was published or updated. (The [jekyll-last-modified-at](https://github.com/gjtorikian/jekyll-last-modified-at) plugin is supported to help provide post modification times).
53
+
54
+
```yml
55
+
feed:
56
+
updated: latest_post
57
+
```
58
+
48
59
### Optional front matter
49
60
50
61
The plugin will use the following post metadata, automatically generated by Jekyll, which you can override via a post's YAML front matter:
0 commit comments