Merge Patterns

Monday is Merge Day

1 in 5 PRs merge on Monday. Friday deployments? Not as common as you think.

19%

Monday Merges

658,296 PRs

Based on 3,387,250 merged PRs | GitHub Archive / BigQuery | December 2024

The Weekly Pattern

When does code actually ship? Our analysis of 3,387,250 merged PRs reveals a clear pattern: Monday dominates, Friday surprises, and weekends are busier than you'd expect.

PR Merges by Day of Week

MonTueWedThuFriSatSun0%5%10%15%20%
DayPRs Merged% of Total
Monday658,29619.08%
Tuesday622,72218.05%
Wednesday500,48514.51%
Thursday480,40113.93%
Friday481,76813.97%
Saturday317,6489.21%
Sunday388,06211.25%

The Monday Surge

Monday isn't just another day—it's when nearly 1 in 5 PRs get merged. That's 658,296 pull requests in our dataset, more than any other day of the week.

Why? The pattern suggests a clear workflow: PRs get opened throughout the week, reviews pile up, and then everything clears out Monday morning.

Fresh Start Effect

Engineers clear their review queues first thing Monday. That Friday PR? It finally gets approved.

Weekend Processing

CI/CD pipelines run over the weekend. By Monday, automated checks have completed and PRs are ready to merge.

"Monday isn't just the start of the work week—it's when 1 in 5 PRs finally get merged."

The Friday Myth

"Don't deploy on Friday" is practically an engineering proverb. But how much code actually ships on Friday?

13.97%

Friday Deployments

Only 481,768 PRs merged on Fridays—less than Tuesday, Wednesday, or Thursday.

Friday actually has the lowest merge rate of any weekday. Engineers either finish their work earlier in the week, or they consciously avoid shipping before the weekend.

"Friday deployments? Only 14% of code ships then."

Weekend Warriors

Here's the surprise: weekends aren't as quiet as you'd think. Combined, Saturday and Sunday account for 20.5% of all merges—roughly 705,710 PRs in our dataset.

Sunday

11.25%

388,062 PRs merged

Saturday

9.21%

317,648 PRs merged

Interestingly, Sunday sees more merges than Saturday. This could be engineers preparing for Monday, automated processes running on a schedule, or global teams where Sunday is a workday.

🔥 Our Take

The Monday spike tells us something important: reviews queue up over the weekend and get cleared Monday morning.

If your team struggles with review latency, look at your Friday afternoon habits. Are PRs sitting in review queues over the weekend? Consider setting a "merge by Thursday" goal for work-in-progress PRs, or schedule dedicated review time early in the week.

What This Means for Your Team

Schedule Reviews Wisely

If reviews pile up by Friday, they'll sit until Monday. Consider a Thursday review push to keep PRs moving.

Plan for Monday Load

Monday sees the highest merge volume. Ensure your CI/CD can handle the surge, and have on-call engineers ready for issues.

Acknowledge Weekend Work

20% of merges happen on weekends. If that's coming from your team, it might signal workload issues—or just timezone differences.

The "No Friday Deploy" Rule Works

Friday has the lowest weekday merge rate. Whether by policy or instinct, engineers are already avoiding Friday deployments.

Related Research

Methodology

This analysis is based on 3,387,250 merged pull requests from GitHub Archive / BigQuery during December 2024. Merge day is determined by the UTC timestamp of the merge event. For full methodology, see the complete study.

See your team's merge patterns

CodePulse shows you when your team ships code and where the bottlenecks are.