From: "Jakub Narębski" <jnareb@gmail•com>
To: Ernesto Maserati <ernesto.2.maserati@gmail•com>, git@vger•kernel.org
Subject: Re: How to generate feature branch statistics?
Date: Wed, 20 Jul 2016 20:10:54 +0200 [thread overview]
Message-ID: <578FBEAE.9080307@gmail.com> (raw)
In-Reply-To: <578F8306.3070306@gmail.com>
W dniu 2016-07-20 o 15:56, Jakub Narębski pisze:
> W dniu 2016-07-20 o 10:05, Ernesto Maserati pisze:
>
>> I assume that feature branches are not frequently enough merged into
>> master. Because of that we discover bugs later than we could with a more
>> continuous code integration. I don't want to discuss here whether feature
>> branches are good or bad.
>>
>> I want just to ask is there a way how to generate a statistic for the
>> average duration of feature branches until they are merged to the master? I
>> would like to know if it is 1 day, 2 days or lets say 8 or 17 days. Also it
>> would be interesting to see the statistical outliers.
>>
>> I hope my motivation became clear and what kind of git repository data I
>> would like to produce.
>>
>> Any ideas?
>
> There are at least two tools to generate statistics about git repository,
> namely Gitstat (https://sourceforge.net/projects/gitstat) and GitStats
> (https://github.com/hoxu/gitstats), both generating repo statistics as
> a web page. You can probably find more... but I don't know if any includes
> the statistics you need.
>
> I assume that you have some way of determining if the merge in 'master'
> branch is a merge of a topic branch, or of long-lived graduation branch
> (e.g. 'maint' or equivalent). To simplify the situation, I assume that
> the only merges in master are merges of topic branches:
>
> git rev-list --min-parents=2 master |
Self correction: Here you need to use --first-parent, as in Peff answer
(which also uses less git invocations, and less of git porcelain).
I wonder if it is something that libgit2 would be helpful...
--
Jakub Narębski
prev parent reply other threads:[~2016-07-20 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 8:05 How to generate feature branch statistics? Ernesto Maserati
2016-07-20 13:14 ` Jeff King
2016-07-20 18:49 ` Junio C Hamano
2016-07-20 23:10 ` Jakub Narębski
2016-07-20 23:31 ` Junio C Hamano
2016-07-20 13:56 ` Jakub Narębski
2016-07-20 18:10 ` Jakub Narębski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=578FBEAE.9080307@gmail.com \
--to=jnareb@gmail$(echo .)com \
--cc=ernesto.2.maserati@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox