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

Unfetched vs zero issues #71

Open
gordongli opened this issue Feb 13, 2018 · 1 comment
Open

Unfetched vs zero issues #71

gordongli opened this issue Feb 13, 2018 · 1 comment

Comments

@gordongli
Copy link

gordongli commented Feb 13, 2018

Since it is difficult to track whether ghcrawler has completed crawling for a repository's data, it would be nice for Measure to determine whether there are actually no issues for a repository vs not having fetched them yet. This would help with automating the currently manual commands to queue the unfetched repositories and start ghcrawler.

One approach could be to use the Github API v3 to GET /repos/:owner/:repo's open_issues_count field. (See https://developer.github.com/v3/repos/#get)

WARNING: there are no issues recorded for the ${owner}/${repo} 
  repository. This may just be because we haven't fetched that data 
  yet.
@jeremy-lq
Copy link
Collaborator

+1 to the desire for automation. We're looking into a couple solutions now, and will update when we have a solid to implement.

stuartlangridge added a commit that referenced this issue Feb 16, 2018
…ed data be a bit more informative (thank you to @gordongli for the suggestion in #71, and this should go some way towards fixing that)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants