Repository navigation
Order entries by publication time - #7
Merged
Merged
Conversation
Deploying blog with
|
| Latest commit: |
a9a4d0b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6a6deb78.blog-9wr.pages.dev |
| Branch Preview URL: | https://chronological-order.blog-9wr.pages.dev |
kitamura-tetsuo
marked this pull request as ready for review
October 29, 2026 11:50
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
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.
Sort English, Japanese and project listings newest-first using timezone-aware publication timestamps. When an exact production publication time is unavailable, the existing entries use their documented first-merge time as an ordering fallback; articles first merged together retain an explicitly indeterminate relative order.
Validation: ordering regression tests cover same-day times, timezone boundaries, fallback and ties; Astro generated 22 pages; listing order was checked across five views; the schema rejected a timestamp without a timezone. The remote tree matches the validated local tree.