search

xtrasmal / gitinspector

Automatically exported from code.google.com/p/gitinspector
GNU General Public License v3.0
0 stars 0 forks source link

Support for multiple repositories #24

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I would like gitinspector to be able to generate a combined report for multiple 
git repositories.

Original issue reported on code.google.com by lapoussi...@gmail.com on 2 Feb 2014 at 5:25

GoogleCodeExporter commented 9 years ago 
Hi.

I have considered this feature before and I don't really know the way to go 
when implementing it. As far as I can see, there are two options here:

1. The statistics from the different repositories could be merged to create a 
truly merged report that still looks like it is from just one repository. Even 
if this could be really useful, the problem with this approach is that 
duplicate rows (or rows very similar to each other with just different 
white-spaces) would be counted as unique rows - simply because we can't use git 
to track them as they are in separate repos.

2. We could just create a separate report from each repo and just spit it out 
the same as when running gitinspector multiple times. In the HTML output it 
could just generate separate tabs for each repo and present them on the same 
page.

Then again; we could just introduce a --merge flag in order to switch between 
(1) and (2).

I'm open for ideas and feedback on how to ac actually go about it. This is 
probably something that would be great to include in 0.4.0, so I'm tagging it 
for that release (for now).

/Adam Waldenberg

Original comment by gitinspe...@ejwa.se on 3 Feb 2014 at 6:33

GoogleCodeExporter commented 9 years ago 
I have a feeling that by 1 you mean combining repository information at data 
collection stage. Don't you think it can be done when post-processing 
per-repository reports instead, disregarding cross-repository row duplicates 
completely?

Say repo1 generates the following «historical commit information» 
(Author/C/I/D) report section:

Hugo Doom : 52 : 389 : 291
Lisa Hacker : 29 : 302 : 156

And repo2 generates this:

Hugo Doom : 23 : 144 : 913
Lisa Hacker : 73 : 2102 : 378

The corresponding section from the combined report would then be:

Hugo Doom : 52+23 : 389+144 : 291+913
Lisa Hacker : 29+73 : 302+2102 : 156+378

(Turns out I don't know how changes percentage is calculated so I omitted it. 
But if in repo1 changes of an author are calculated as B1/T2 and in repo2 it is 
B2/T2, the combined value should be (B1+B2)/(T1+T2))

Original comment by lapoussi...@gmail.com on 4 Feb 2014 at 12:06

GoogleCodeExporter commented 9 years ago 
Your example describes exactly how I imagine (1) would work.

/Adam Waldenberg

Original comment by gitinspe...@ejwa.se on 8 Feb 2014 at 1:27

GoogleCodeExporter commented 9 years ago

Original comment by gitinspe...@ejwa.se on 24 Nov 2014 at 8:03

GoogleCodeExporter commented 9 years ago 
Is there any workaround for this??

Original comment by julioarg...@gmail.com on 14 May 2015 at 9:03

GoogleCodeExporter commented 9 years ago 
Using gitsubtree is a easy workaround to retrieve stats from different 
repositories

Original comment by julioarg...@gmail.com on 14 May 2015 at 12:28

GoogleCodeExporter commented 9 years ago 
That's probably the best option until this is actually properly implemented.

/Adam Waldenberg

Original comment by gitinspe...@ejwa.se on 15 May 2015 at 8:58