Commit list "Commits on …" date headers use a stale account timezone, not my browser timezone #199224
Replies: 3 comments
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
Body
On a repository's commit list (
/commits/<branch>), the "Commits on " group headers are grouped using a timezone that does not match my browser or thetzcookie. A commit that displays as "Jun 16, 2026, 8:16 PM GMT-3" appears under a "Jun 17, 2026" header.Evidence (from the page's own embedded data, inspected in-browser)
America/Sao_Paulo(UTC-3);tzcookie =America/Sao_Paulo.authoredDate=2026-06-16T20:16:22-03:00(instant2026-06-16T23:16:22Z).<relative-time>correctly renders "Jun 16, 2026, 8:16 PM GMT-3".payload.commitGroups[].titlefor that commit is "Jun 17, 2026" — which only matches a UTC+2 rendering of that instant.?nocache=1), and regardless of the commit's stored git offset (rewriting the author offset to -03:00 did not change the header).Expected
Group headers should use the same timezone as the per-commit timestamps shown on the same page (my browser /
tzcookie), so a commit shown at "8:16 PM Jun 16 GMT-3" is grouped under "Jun 16".Actual
Headers are computed server-side in a stale account timezone (UTC+2 in my case, apparently retained from prior API activity from another region) that never updates to my real timezone — even though the docs state the timezone updates when browsing the website.
Impact
Commits appear under the wrong calendar day, making history confusing to scan. This looks like the same family of cross-surface timezone inconsistency reported in #22251 (commit time vs Blame).
Reproduction in a public repo — proof it is server-side, not our commits
Public repo: https://github.com/Quartel-Enterprise/bible-planner-mobile-client/commits/main
Every recent commit is a GitHub squash-merge (
committer = GitHub <noreply@github.com>), so GitHub stamps the dates, not us. Three independent proofs the+02:00comes from GitHub:1. GitHub writes two different offsets on the same commit. Commit
03fa023hasauthor 2026-06-17 01:16:22 +0200butcommitter 2026-06-16 20:16:22 -0300— the same instant (2026-06-16T23:16:22Z), two different offsets, both written by GitHub. We chose neither.2. GitHub re-stamps our author date on squash-merge. Our branch commit for that PR was authored
2026-06-16 20:09:45 -0300(our machine, our timezone). After "Squash and merge", GitHub rewrote it toauthor 2026-06-17 01:16:22 +0200. We wrote-03:00; GitHub wrote+02:00.3. Forcing the commit to
-03:00does not move the header. I rewrote that commit's author offset to2026-06-16 20:16 -03:00(matching my browser andtzcookie) and force-pushed. The commit-list header still read "Jun 17" — confirming the grouping ignores the commit entirely and uses a server-side account timezone.Beta Was this translation helpful? Give feedback.
All reactions