Databases
StackOverflow2013
Postsdbo
POGIT - Determining # lines of code written per hour (committed & uncommitted)
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGIT - Determining # lines of code written per hour (committed & uncommitted)
    primarykey
    data
    text
    <p>I want to graph the # of new lines of code written each hour over the course of the day.</p> <p>I'm aware of git diff, git log and they are very powerful for determining total # of lines committed to a branch. The --since="7am" option is really great as well.</p> <p>Some of the git commands I'm utilizing are:</p> <p><strong>Total # of lines</strong> </p> <pre><code>git log --numstat --pretty="%H" master | awk 'NF==3 {plus+=$1; minus+=$2} END {printf("+%d, -%d\n", plus, minus)}' </code></pre> <p><strong># lines additional in devel branch compared to master</strong></p> <pre><code>git log --numstat --pretty="%H" master..devel | awk 'NF==3 {plus+=$1; minus+=$2} END {printf("+%d, -%d\n", plus, minus)}' </code></pre> <p><strong># lines since a time of day</strong></p> <pre><code>git log --since="7am" --format=format: --numstat | awk 'NF==3 {plus+=$1; minus+=$2} END {printf("%d, -%d\n", plus, minus)}' </code></pre> <p><strong># lines currently uncommitted</strong></p> <pre><code>git diff --stat | tail -1 | awk '{print $4}' </code></pre> <p>I've been struggling though with coming up with a way to track the # of new lines written in the past hour including uncommitted changes, across all branches in the current repo.</p> <p>This may be more of a math problem.</p> <h1>The Question:</h1> <ul> <li>How can I determine the exact amount of lines written in the past hour across all branches, including uncommitted changes.</li> </ul> <h1>Gotchas/Scenarios:</h1> <ul> <li>+200 uncommitted at 7pm is 200 new lines written. +250 uncommitted at 8pm is only 50 new lines written the past hour.</li> <li>+200 uncommitted at 7pm is 200 new lines written. At 8pm we commit 100 of the lines and then write 50 more new lines. Now +150 show as uncommitted, but we would need to determine that only 50 new lines were written in the past hour. Reconciling committed and uncommitted stats.</li> <li>+200 uncommitted at 7pm. At 7:30pm we write 500 additional new lines and commit them. At 8pm we write 100 more new lines thus showing +300 as uncommitted. We should end up with 600 new lines written in the last hour.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCœur
    1. USNick Carson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGIT - Determining # lines of code written per hour (committed & uncommitted)
      1. USNick Carson
      1. VTFavorite
    2. VO
      singulars
      1. POGIT - Determining # lines of code written per hour (committed & uncommitted)
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POGIT - Determining # lines of code written per hour (committed & uncommitted)
      1. USBob Gilmore
      1. VTFavorite
    1. COBecause of the Gotchas you mention, you're probably going to have to go with a solution that stores the last run's results (in a file, DB, in the repository with `git config`, etc.) and then compares this time's results against them. The simplest of the storage options for keeping the last value is probably the `git config` one, but since you want to keep historical data to graph, you probably want a simple database anyway. If you already have a running database server, you could use it, or you could use a file-based DB like SQLite.
      singulars
      1. POGIT - Determining # lines of code written per hour (committed & uncommitted)
      1. USMoshe Katz
    2. COYep, got a MySQL database to store total lines of code ever added, and the # of lines COMMITTED in the past hour. I'm still a bit unsure how to approach assessing the uncommitted lines of code without double counting it.
      singulars
      1. POGIT - Determining # lines of code written per hour (committed & uncommitted)
      1. USNick Carson
    3. COCompare the uncommitted lines from this run with the total of uncommitted from last run and committed from this run. The difference will be the number of new lines. For your first example: 250 + 0 - 200 = 50. For your second example: 150 + 100 - 200 = 50. For your third, 300 + 500 - 200 = 600.
      singulars
      1. POGIT - Determining # lines of code written per hour (committed & uncommitted)
      1. USMoshe Katz
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload