git/list[1] front-page[2] threads[3] people[4] search[5] about
 

How to generate feature branch statistics?

From
EMErnesto Maserati <ernesto.2.maserati@gmail.com>
Date
Jul 20, 2016, 08:05 UTC
Message-ID
<CAOHAwykGkfY7M30jT8t0k6Gsdy5QSBHmAPiWYoKibjUgS-G6hg@mail.gmail.com>

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?
Next: Jeff King
Message 1 of 7 in “How to generate feature branch statistics?”
  1. Ernesto MaseratiJul 20, 2016
  2. Jeff KingJul 20, 2016
  3. Junio C HamanoJul 20, 2016
  4. Jakub NarębskiJul 20, 2016
  5. Junio C HamanoJul 20, 2016
  6. Jakub NarębskiJul 20, 2016
  7. Jakub NarębskiJul 20, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.