Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Hot" files #13

Open
mihneadb opened this issue Dec 7, 2013 · 2 comments
Open

"Hot" files #13

mihneadb opened this issue Dec 7, 2013 · 2 comments
Labels

Comments

@mihneadb
Copy link
Contributor

mihneadb commented Dec 7, 2013

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
Copy link

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
Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants