I was bored, really bored into bones. I looked into StackOverflow.com’s unanswered questions, but trying to solve P vs. NP problem might be even easier than answering those.
Like a drama, someone dies; or a chick flick, Susan caught her cheating boyfriend. Anyway, out of nowhere, I thought what about issues or bug reports?
A random issue, you don’t specify particular project or whatsoever thing. Like you see on StackOverflow, the questions are ranging from nothing to everything you don’t even have a thought or give a damn before.
I checked out GitHub API and bitbucket API, neither can do without specifying repo and/or user who owns or forks the repo. So, API is a dead end.
But I find another way to search for the unresolved issues with ugly keywords:
site:github.com inurl:issues intitle:issue -"closed the issue" -"This issue was closed" site:bitbucket.org -inurl:"issues" intitle:"issues" -"from * to resolved" -"from * to invalid" -"from * to duplicate" -"from * to wontfix"
They are super ugly, but work. You may want to append the languages you want or you don’t want to see to the keywords.
Here are search links for unresolved issues on GitHub and Bitbucket.
I don’t know what database designs they use, but it should not be a problem to do a query for issues across all repos. But it will need to have time setting for issues have not been resolved after # days, or sort of. There is not much need to find a fresh unresolved issues. (I hate people rushing to answer a new question on StackOverflow)
If they want to expand the community aspect, this would be a nice feature in my opinion. There are a lot of bored coders, who can’t sleep.
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.