27% of code ships on weekends—what our data reveals about work-life balance in tech
Weekend Code Pushes
Saturday + Sunday combined
Based on 3,387,250 merged PRs | GitHub Archive / BigQuery | December 2024
We analyzed 3,387,250 merged pull requests to understand when engineers are actually pushing code. The results paint a striking picture of modern engineering culture.
Weekend Pushes
More than 1 in 4 pushes
After-Hours PRs
Opened outside 9-17 UTC
Peak Hours
Highest activity window
More than 1 in 4 code pushes happen on Saturday or Sunday. That's not a small minority—it's a significant portion of engineering work happening outside traditional work hours.
15.47%
More pushes than Saturday
12.18%
The "quieter" weekend day
Perhaps the most telling detail: Sunday sees more code pushes than Saturday. Engineers aren't just casually tinkering on weekends—they're preparing for Monday, catching up on work, or responding to production issues.
"27% of code pushes happen on weekends. The always-on culture is real—and it's in the data."
Here's the number that should concern every engineering leader: 64% of pull requests are opened outside traditional business hours (9 AM - 5 PM UTC).
Nearly two-thirds of all pull requests are opened before 9 AM or after 5 PM UTC. This includes evenings, early mornings, and weekends.
Some of this is explained by global teams spanning time zones. But even accounting for distributed work, the sheer volume of after-hours activity suggests that many engineers are working outside reasonable boundaries.
The highest concentration of code pushes happens in the late afternoon UTC, overlapping with morning in the Americas and end-of-day in Europe.
"64% of PRs are opened outside 9-5. The workday has no boundaries."
These numbers don't tell us why engineers work weekends and after hours. The reasons vary:
Many open source contributions happen on personal time, by choice. Side projects and learning often happen outside work hours.
Teams span time zones. Someone's weekend is another person's Tuesday. This is a natural consequence of distributed work.
Crunch time is real. Unrealistic deadlines push work into evenings and weekends. The code ships, but at what cost?
Some organizations celebrate the "hustle." Visibility becomes tied to availability. Weekend commits signal dedication.
This data should be a wake-up call, not a badge of honor.
We're not naive—some weekend and after-hours work is inevitable and even welcome. Distributed teams, personal passion projects, and the occasional production incident are facts of engineering life.
But when 27% of code ships on weekends and 64% of PRs happen after hours, something is structurally broken. This isn't occasional crunch—it's systemic.
The question isn't whether your team works weekends. It's whether they have to.
Engineering leaders should track these patterns for their own teams. If weekend work is spiking, ask why. Is it deadlines? Understaffing? Cultural pressure? The data won't tell you, but it will tell you to start asking.
Track when code is being pushed on your team. If weekend commits are rising, investigate before burnout hits. The data is in your Git history.
Leaders should model sustainable work. If the VP of Engineering is pushing code at midnight, that sets expectations. Slack status, commit times, and response patterns all signal culture.
Weekend open source contributions are healthy. Mandatory weekend deploys are not. Make sure your team knows the difference—and feels it.
If certain team members consistently work weekends while others don't, you may have a workload imbalance. Use data to identify patterns before they become resignations.
"Sunday has more code pushes than Saturday. Engineers aren't resting—they're preparing for Monday."
"Peak activity at 14:00-18:00 UTC—when the Americas wake up and Europe winds down. The global handoff is real."
"The question isn't whether your team works weekends. It's whether they have to."
This analysis is based on 3,387,250 merged pull requests from GitHub Archive / BigQuery during December 2024. "Weekend" is defined as Saturday and Sunday UTC. "After hours" is defined as outside 9:00-17:00 UTC. Push timestamps are based on the Git commit date. For full methodology, see the complete study.
CodePulse shows you when your team is working and helps identify sustainability risks before they become burnout.