Fun to see this up here. Originally when I built this there was some discussion on whether it made any sense to show a global view; most people are just going to use the issues dashboard to look at their own issues, obviously. Honestly, I just thought it was cool to have filters across the whole site, so I left it in (which was only an option given how quick it was to calculate and return these results in Elasticsearch — that's also part of the reason the numbers are fluctuating a bit, as some have pointed out here).<p>Still wish more people knew about this dashboard view into Issues. Even though it's now a prominent link in the header, I don't think the page got to be something I was really happy with — most of the work was done in the final week before we shipped Issues, so it was somewhat an afterthought. There's a ton of power in there, but it's hidden away behind an arcane syntax that I, the creator of the damn thing, can't really remember at this point, two years later, ha. Still dig the overall motivation behind the page, though!
Sorted by +1s: <a href="https://github.com/issues?q=is%3Aopen+is%3Aissue+sort%3Areactions-%2B1-desc" rel="nofollow">https://github.com/issues?q=is%3Aopen+is%3Aissue+sort%3Areac...</a><p>Here are the top three:<p>1. Contribution graph can be harmful to contributors (<a href="https://github.com/isaacs/github/issues/627" rel="nofollow">https://github.com/isaacs/github/issues/627</a>)<p>2. proposal: generic programming facilities (<a href="https://github.com/golang/go/issues/15292" rel="nofollow">https://github.com/golang/go/issues/15292</a>)<p>3. Proper tabs for open files (<a href="https://github.com/Microsoft/vscode/issues/224" rel="nofollow">https://github.com/Microsoft/vscode/issues/224</a>)<p>Can't say I'm terribly surprised!
6,6 Mio open issues created by GoogleCodeExporter.
<a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+author%3AGoogleCodeExporter" rel="nofollow">https://github.com/issues?q=is%3Aissue+is%3Aopen+author%3AGo...</a>
Even though there are several open issues in github, how can someone with little development experience or newbie can start contributing.<p>On asking this question, many may suggest that first we should use the particular piece of code in own project and contribute on that project by raising issues or fixing them. As a beginner, people may start using very popular frameworks like Ruby on Rails or Node.js. Considering it's complexity or maturity, it's extremely difficult if not impossible to start contributing.<p>I am thinking, somewhere down the line, there is some form of hand holding or mentor ship needed. Where mentor give small task, help in giving some tips or advice, review the first pull request etc. This will definitely boost contribution to opensource projects.<p>There may be several people providing mentor ship. But I feel it's not structured, how a newbie knows there exist someone who is willing to help. Only way I can think of now is to spam lot of people randomly by looking at their github profiles.<p>Please suggest how to encouraging new developer to contribute more to opensource and help closing the open issues.
I wonder if one day GitHub will announce the World's Issue Closing Day. The day every programmer will try hard to close their issues. Though, isn't it what we do every day?
55,272 of those are marked as "help wanted" -- feeling bored?<p><a href="https://github.com/issues?utf8=&q=is%3Aopen+is%3Aissue+label%3A"help+wanted"" rel="nofollow">https://github.com/issues?utf8=&q=is%3Aopen+is%3Aissue+label...</a>
A bit late to the party. I find that many maintainers are left with a mountain of issues and very few eyeballs to help process them. I made a tool that helps others get involved with your open source projects to, hopefully, help keep your issue count manageable. Check it out: <a href="https://www.codetriage.com" rel="nofollow">https://www.codetriage.com</a>
Why is the default issue filter "is:open"? When I have an issue with a project, I never want to restrict focus to open issues. In fact, I'd much rather land on a closed issue where it turns out the issue was recently fixed, or there is a workaround, a better approach, etc.
Interestingly enough, when refreshing the count of closed varies wildly, and when looking at closed issues, the count of open varies wildly +/- a few million. I wonder what causes that.
404 already<p>Edit: not sure what makes this comment so controversial (at least 5 downvotes already) , the link does indeed 404 if you aren't logged in.
This is a nice query[1] to view all open issues for your org's private repos:<p><a href="https://github.com/issues?q=is%3Aopen+is%3Aissue+is%3Aprivate" rel="nofollow">https://github.com/issues?q=is%3Aopen+is%3Aissue+is%3Aprivat...</a>
I love github ... but sometimes it also contains incredible idiocy stuff: The most commented stuff of nothing! +16000 comment of wind -> <a href="https://github.com/issues?q=is%3Aopen+is%3Aissue+sort%3Acomments-desc" rel="nofollow">https://github.com/issues?q=is%3Aopen+is%3Aissue+sort%3Acomm...</a> <a href="https://github.com/peej/to.uri.st/issues/128" rel="nofollow">https://github.com/peej/to.uri.st/issues/128</a>
This number sounds like the number of unread emails in some inboxes. Some have embraced Inbox Zero - is there a similar movement for issues, something like "Bug Zero"?
So if creating Wikipedia took 100 million hours, closing the worlds GitHub issues might be a task about one order of magnitude smaller than creating Wikipedia...
<a href="https://github.com/wting/autojump/issues/353" rel="nofollow">https://github.com/wting/autojump/issues/353</a> - Yay I'm mentioned in one of the github open issues (Which actually isn't a issue anymore). Wonder how many such open issues are present, which are worth closing!
So, roughly a third of all issues are open. I think it would be nice if GitHub create a daily/weekly/monthly/annual "State of the Hub" kind of analysis for the entire ecosystem with drill downs and stuff.
It's a SHAME Github is trying to protect its search <i>results</i>.<p>I am often left in front of this situation when hunting for code using advanced search parameters -- they are preventing people from searching efficiently.<p>Does anyone know what is their motivation behind this?