Timezone-aware contribution graphs
Today we’ve made your contribution graphs timezone-aware. GitHub is used everywhere and we want to reflect that in our features. If you happen to work from Japan, Australia or Ulan…
Today we’ve made your contribution graphs timezone-aware. GitHub is used
everywhere and we want to reflect that in our features. If you happen
to work from Japan, Australia or Ulan Bator, we want to count your contributions
from your perspective.
When counting commits, we use the timezone information present in the timestamps for those commits.
Pull requests and issues opened on the web will use the timezone of your
browser. If you use the API you can also specify your timezone.
We don’t want to mess up your current contribution streaks, so only
contributions after Monday 10 March 2014 (Temps Universel Coordonné) will be timezone-aware.
Enjoy your time(zone)!
Tags:
Written by
Related posts
What 986 million code pushes say about the developer workflow in 2025
Nearly a billion commits later, the way we ship code has changed for good. Here’s what the 2025 Octoverse data says about how devs really work now.
Introducing Agent HQ: Any agent, any way you work
At Universe 2025, GitHub’s next evolution introduces a single, unified workflow for developers to be able to orchestrate any agent, any time, anywhere.
Octoverse: A new developer joins GitHub every second as AI leads TypeScript to #1
In this year’s Octoverse, we uncover how AI, agents, and typed languages are driving the biggest shifts in software development in more than a decade.