To provide an answer to the question "How did the no. of commits for Java projects change over years?"

[fernandocastor]

We need to implement and test the features required to use Groundhog to answer the question in the title of the issue. We then have to use it to actually answer the question.

[gustavopinto]

It will be very difficult to answer this question, mainly because the github api only brings the last 30 commits of a project. Unless we download the projects and then analyze one by one.

[fernandocastor]

But you can get the commits by interacting directly with the git repository, can't you?

[jesusjackson]

I was reading in the github api and i think it's possible, but i'm trying to figure out a way to do this sending a year and receiving only commits done in that year.

[jesusjackson]

@fernandocastor this question is for one project or do i have to do a mean for every java project and give a result for a number of years?

[fernandocastor]

Ideally, for a large number of projects. SUmmarizing that information is not so simple.

[jesusjackson]

@gustavopinto i went to search for the code i did for the Issue #48 and found it was all deleted.

[gustavopinto]

@pork9 yes. I have moved it to here. All code related to answer an issue should be there instead in groundhog.

[rodrigoalvesvieira]

👍

[jesusjackson]

@gustavopinto Thanks, i'll change it so it answers this question, let me ask you something. How did set for the groundhog-case-study to use groundhog even without the groundhog code present?

[jesusjackson]

And i didn't find a way to get more then 30 commits. I'm really worried about that.

[gustavopinto]

dont worry. we should analyze local commits instead of rely on github commits api. it is currently under development in this branch cd8c27f