Open geerlingguy opened 9 years ago
While git doesn't make this easy, you could compile a list of commit hashes for each branch and then diff them going back to 6.x. i.e. 8.0.x commits are commits that are not found in 7.x, 7.x commits are diffed from 6.x, etc.
edit: The git way of doing this is git branch --contains <commit hash>
, but you would have to do that for every commit in 8.0.x.
That would be easy to create, see this line from json.rb:
log_args = ARGV[0] || '--since=2011-03-09'
git_command = 'git --git-dir=../drupalcore/.git --work-tree=drupal log 8.0.x ' + log_args + ' -s --format=%s'
Ah, that would work as well for how Drupal is developed (ex: 7.x is never randomly merged into 8.0.x). So we would just keep track of the branch creation date and use that for --since
.
It would be also nice to see overall commit amount for contribs. I think we might need to get the database setup for this because this starts to get complicated
Is it possible to make it so this project compiles info for arbitrary versions of Drupal Core? (e.g. 6.x, 7.x, 8.0.x, 9.0.x, etc.)
I think it'd be nice (especially considering this is by far the most used metric for core contributions I've seen passed around the community) if we can gain better insight to members of the community who have helped with past versions... and also be able to easily switch to the newer HEAD branch once 8.x versions are mainstream.