Merge automation report for

https://github.com/violetaGitHub/AspNetCore

Full merges that can be automated (entire branch or pull request)

Automatic merges

19.32%

222 manual merges are automatic using mergedroid

Time Saved

55.50h

Reduction in manual merge resolution time, context switching and lost focus *

Individual file merges that can be automated (even when the entire branch/PR can’t be)

Automatic file merges

45.43%

2336 manual file merges are automatic using gmaster

Time Saved

116.80h

Reduction in manual file merge resolution time, context switching and lost focus **

Problem detected

222 merges required manual intervention and consumed around 55.50h of developer time

2336 file merges required manual intervention and consumed around 116.80h of developer time

Solution proposed Solution proposed

Install mergedroid in your GitHub repo and save time in future merges

Use gmaster as Git GUI or alternatively install SemanticMerge for future merges

Detailed report

Full merge automation

Means the entire merge can be automated, whether it is 1 file or 100, the system won’t ask any questions.

Total merges processed

4275

Merges that require manual intervention with GitHub

1149

Merges that require manual intervention with mergedroid

927
(19.32% better than GitHub)

File merge automation

Sometimes the entire merge can be automated because one of the files to be merged needs manual intervention. Even when that happens, gmaster or semanticmerge will be of great help.

Total merged files

7407

Manual merges of supported file types (C, C++, Java, C#)

File merges that require manual intervention with Git

5142

File merges require manual intervention with gmaster/semanticmerge

2806
(45.43% better than GitHub)

Manual merges of unsupported file types (binaries, not supported languages)

0

Time reduction Estimations

* Our metrics say that developers spend about 15 minutes each time a branch or pull request can’t be merged automatically. It counts time between you stop the task you are working on to fix the merge until you return to it. It includes time to switch to a different branch, stash or checking work in progress, etc. Merges with manual intervention mean nasty context switching, one of the key productivity killers.

** Our metrics say that manually solving a conflict takes 3 minutes in average. This time just includes interaction with the merge tool. It doesn’t include context switching time since we already consider the developer is in the middle of a manual merge, already pulled the repo, switched to the branch, etc.