Home Education Open source projects: merging schedules

Open source projects: merging schedules

Author

Date

Category

When do open source projects merge their pull requests?

I was curious about the merging time patterns of pull requests from open source projects. So I extracted all the merging events from Github during the month of October, and plotted them. A total of 441,927 merged pull requests were analyzed (here’s the data).

Let’s take a look into it.

open source projects
Number of pull request merges per hour

You can see that there’s an interesting build up during the day.

Teams prefer to merge their pull requests during the afternoon.

As the day moves on, there is a merging build up in an interesting saw effect.

3pm seems to be the prefered time to merge.

Number of pull request merges per day of the week
Number of pull request merges per day of the week

If we turn attention to the days of the week we also see some interesting data points come out.

Developers prefer to merge on Thursdays and there’s a clear build up from Monday to Thursday and then it comes down on Friday.

There’s a surprising number of merges in the weekend. This might be something present in open source projects but maybe not true for all industry.

Looking at this chart, you can also see when features/bug fixes tend to be finished. Teams prefer to finish features on Thursday.

This might be interesting also because it shows clear preference between hours of the day and days of the week. So the next time you’re planning your sprint, bear this in mind.


Edit: We just published an ebook: “The Ultimate Guide to Code Review” based on a survey of 680+ developers. Enjoy!


About Codacy

Codacy is used by thousands of developers to analyze billions of lines of code every day!

Getting started is easy – and free! Just use your  GitHub, Bitbucket or Google account to sign up.

GET STARTED

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Subscribe to our newsletter

To be updated with all the latest news, offers and special announcements.

Recent posts

7 drawbacks of linting tools

Linting tools (also known as linters or static analyzers) help automate the code review process. They perform basic static code analysis by flagging programming...

Using the API to add Codacy Grade details to the Readme

Some context Codacy has a badge mechanism that can be included in your Readme file. It gives you an idea of the grade of your repository, from...

March Product Update: Support for Cloud Infrastructure-as-code, Custom Reports with API endpoints & more 🚀

Here are some fresh updates from March! This month we bring you a new product offering, new features, and product updates, interesting reads, and...

Top 10 ways to perform fast code review

We always want to be fast at code review.. How frequent is it for you to be reviewing code at 3am? When code reviewing, do you...

Interview with Gary McKay, Somos’ Director of Agile Service Delivery

Somos is a proven leader in registry management and data solutions. Somos fosters meaningful connections by delivering value, innovation and confidence to consumers. We...