"Hot" files

[mihneadb]

Files that have been changed in the past month in more than one commit.

In order to get this data, we need to access the commit data API. Basically, for a push event, we have to iterate through the commits, acces the API URL for every one of them and store the reply as a "commitevent" document (see schema.md).

From there, just have to check the "filename" attribute for every entry inside the "files" array for the respective commitevents.

[bogdans83]

I'm thinking of the need of such a query: knowing that file is rather important to the organization and you should read it? But doesn't seem to bring that much benefit.

Why did you find this useful?

[mihneadb]

Also docs might need updating or it might be a good candidate for
refactoring?

On Mon, Dec 23, 2013 at 3:21 PM, Bogdan Sandulescu <notifications@github.com

wrote:

I'm thinking of the need of such a query: knowing that file is rather
important to the organization and you should read it? But doesn't seem to
bring that much benefit.

Why did you find this useful?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/13#issuecomment-31118702
.

Mihnea Dobrescu-Balaur