9 ms·
GitHub has 11,995,200 open issues
- ryanlol 10y ago404 already 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.
- Kristine1975 10y agoGitHub now has 11,995,201 open issues.
- sachkris 10y agoIt is not 404. You need to log in.
- Washuu 10y agoThat is a terrible design by them. It should be 403 Forbidden.
- shangxiao 10y agoIt's a pattern to prevent information leakage
- Washuu 10y agoI assume to prevent exposing the names of private repositories, correct? For the main(global) search page it would seem reasonable easy to just omit that from the search results.
- stephengillie 10y agoThis way it can't be brute-scraped either.
- danneu 10y agoThat makes sense for endpoints like /admin, but it's more confusing than it's worth for users when the endpoint is otherwise rather public. Well, just see this comment thread. As an example, in this case with the /issues page, redirecting to `/login?redirect-to=/issues` would be more user-friendly since it signals that the page exists but you must authenticate.
- sachkris 10y agoNo, 403 implies the resource is unavailable even after authorization. 401 Unauthorized maybe the right one here.
- Matt3o12_ 10y agoGiving a 401 indicates that there might be a resource, though, which can also be harmful. It is fairly common to return a 404 to unauthorized users (or users with not enough permission) so you don't give away meta information. Granted, for the public search, it should return an appropriate error code but they should not do that for private repositories. Thus it think it is fair to assume that they have a policy: if user/guest does not have sufficient permission, always return an error 404.
- dayta 10y agoGitHub returns a 404 when you're not logged in, so ryanlol's statement is correct. Just try it, before claiming it is not curl -I https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+ https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Ais...
- striking 10y agoYou can only see the first 400 pages, unfortunately :(
- chrisfosterelli 10y agoI find it particularly odd how the number of results in the top right corner changes depending on what page you're on, as well.
- deleted 10y ago[deleted]
- kristopolous 10y agoHah, after this commit, it'll make it 11,995,199 baby!
- Frenchgeek 10y agoUntil someone smarter than you discover it actually make it 11,995,205 at least...
- masklinn 10y agoDon't you mean 11,995,236?
- jank66 10y ago6,6 Mio open issues created by GoogleCodeExporter. https://github.com/issues?q=is%3Aissue+is%3Aopen+author%3AGoogleCodeExporter https://github.com/issues?q=is%3Aissue+is%3Aopen+author%3AGo...
- githubSearchSUK 10y agoIt's a SHAME Github is trying to protect its search results. I am often left in front of this situation when hunting for code using advanced search parameters -- they are preventing people from searching efficiently. Does anyone know what is their motivation behind this?
- lifeisstillgood 10y agoIt's not going to be an easy job to be fair - I also find the search frustrating - I would appreciate the creation of an overarching (elasticsearch?) index across all their stores but I would quake at implementing it. It's a frustrating thankless task to do it of course, but looking for a competitive moat - that will make gitlab and Atlassian quake.
- holman 10y agoNot really sure what you're getting at, but I'm assuming you mean searching for specific syntax or language aspects. GitHub's definitely not "protecting" shit; it's just that search is a hard problem, and searching code is a really hard problem, at least at the scale they're at. They're running one of the largest Elasticsearch clusters in the world, and a lot of significant things in code are stop words (or not words at all) in most search databases. Not to mention you need to invalidate entire repo indexes when you force push, etc. It just takes a lot of resources, and like anything, will get better over time.
- githubSearchSUK 10y agoI was under the impression that since the page returned 404 after being posted here, they removed the ability to search using these filters, at the very broad range it was used at. Now the page is back and I'm not sure what to make of it.
- deleted 10y ago[deleted]
- M4v3R 10y agoIt has even more (20M) closed issues, which is a sign that on average the OS community is healthy and active :).
- deleted 10y ago[deleted]
- jhgg 10y agoInterestingly 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.
- aiiane 10y agoMy guess? They're giving an estimation based on talking to a few shards of a much larger sharded system rather than trying to actually get canonical results for every shard - since it's unlikely that you need a precise count across that many repositories (which would be really expensive to calculate in real time).
- deleted 10y ago[deleted]
- shoyer 10y agoSorted by +1s: https://github.com/issues?q=is%3Aopen+is%3Aissue+sort%3Areactions-%2B1-desc https://github.com/issues?q=is%3Aopen+is%3Aissue+sort%3Areac... Here are the top three: 1. Contribution graph can be harmful to contributors (https://github.com/isaacs/github/issues/627 https://github.com/isaacs/github/issues/627) 2. proposal: generic programming facilities (https://github.com/golang/go/issues/15292 https://github.com/golang/go/issues/15292) 3. Proper tabs for open files (https://github.com/Microsoft/vscode/issues/224 https://github.com/Microsoft/vscode/issues/224) Can't say I'm terribly surprised!
- anonfunction 10y agoThis is a nice query[1] to view all open issues for your org's private repos: https://github.com/issues?q=is%3Aopen+is%3Aissue+is%3Aprivate https://github.com/issues?q=is%3Aopen+is%3Aissue+is%3Aprivat...
- johndoe90 10y agoI 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?
- labster 10y agoGitHub didn't announce it, but I'm a fan of Bit Rot Thursday: http://blogs.perl.org/users/zoffix_znet/2016/01/bit-rot-thursday.html http://blogs.perl.org/users/zoffix_znet/2016/01/bit-rot-thur...
- pavel_lishin 10y agoTech Debt Thursday would be a little more alliterative.
- labster 10y ago/t/, /d/, and /θ/ are all pretty close, but I've never thought of it as alliteration. But I suppose it does count. Thanks for expanding my literary toolbox.
- therealmarv 10y agoGithub itself has not that much open issues (nobody would use it) ;)
- holman 10y agoFun 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). 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!
- willvarfar 10y agoIssues could be integrated much better with forks. If I have a fork of something, I should see not just issues people post in my repo, but issues people post in other forks. These are differentiated visually, and perhaps don't trigger notifications. When someone fixes the issue in another fork, I should see a 'patch pending' kind of thing, and get a notification.
- robbiemitchell 10y agoThis might be another reason why Holman thinks branches are better than forks. cf. https://twitter.com/holman/status/661365207143333888 https://twitter.com/holman/status/661365207143333888, https://twitter.com/holman/status/661357354827448321 https://twitter.com/holman/status/661357354827448321
- pavel_lishin 10y agoHe seems to think that this is only the case for organizations, not open source projects: https://twitter.com/holman/status/661384740927242240 https://twitter.com/holman/status/661384740927242240
- musicalentropy 10y agoI love this one : "question1-what did you do in the past two years?"
- nikolay 10y agoSo, 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.
- jimmytidey 10y agoSo 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...
- tommorris 10y agoOnce done with that, Wikipedia kinda has a backlog too... https://en.wikipedia.org/wiki/Wikipedia:Backlog https://en.wikipedia.org/wiki/Wikipedia:Backlog
- stephengillie 10y agoThis 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"?
- tonyedgecombe 10y agoI've had a policy of no known bugs for a long time, no matter how trivial they are. I'm lucky though in that I don't have a manager sitting over me measuring my rate of feature creation.
- diimdeep 10y agoAnd it's growing
- butu5 10y agoEven though there are several open issues in github, how can someone with little development experience or newbie can start contributing. 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. 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. 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. Please suggest how to encouraging new developer to contribute more to opensource and help closing the open issues.
- lewispollard 10y agoIRC is often your best bet. If you find a project you'd like to contribute to, see if they have an IRC channel, there will always be regulars there who have a lot of experience with the projects and will almost definitely have advice to give to beginners wanting to contribute.
- 50CNT 10y agoDjango has a django-core-mentorship mailing list[0] for people interested in starting to contribute, a guide on contributing[1] and a selection of issues tagged as easy-pickings[2] that are suitable for beginners to work on. I haven't personally tried it, but I did think it was cool when I stumbled over it. [0][https://docs.djangoproject.com/en/dev/internals/mailing-lists/#django-core-mentorship https://docs.djangoproject.com/en/dev/internals/mailing-list...] [1][https://docs.djangoproject.com/en/dev/internals/contributing/ https://docs.djangoproject.com/en/dev/internals/contributing...] [2][https://code.djangoproject.com/query?status=!closed&easy=1 https://code.djangoproject.com/query?status=!closed&easy=1]
- jsmeaton 10y ago
- tonyedgecombe 10y ago20,928,924 closed so we must be doing something right.
- kek918 10y agoFor a second there I thought GitHub itself had 12 million internal issues
- babo 10y agoPretty misleading title, all open Github projects has that many issues altogether.
- yev 10y agoInteresting to see that whenever one refreshes the page - the number changes. Curious to see issue-per-minute value :D
- daw___ 10y ago55,272 of those are marked as "help wanted" -- feeling bored? https://github.com/issues?utf8=&q=is%3Aopen+is%3Aissue+label%3A"help+wanted" https://github.com/issues?utf8=&q=is%3Aopen+is%3Aissue+label...
- Mikushi 10y agoI am indeed a bit bored, how do you filter by "help wanted" not too clear on this interface.
- daw___ 10y agoYou can use the "label" filter: https://github.com/issues?utf8=&q=is%3Aopen+is%3Aissue+label%3A"help+wanted" https://github.com/issues?utf8=&q=is%3Aopen+is%3Aissue+label... Remember to wrap in quotes multi word labels.
- pavel_lishin 10y agoCan this be filtered by primary project language? I'm not going to be much help to anyone whose project is mostly C or Ruby.
- r3bl 10y agoJust add something like language:Python and you're good to go. :)
- aurelien 10y agoI love github ... but sometimes it also contains incredible idiocy stuff: The most commented stuff of nothing! +16000 comment of wind -> https://github.com/issues?q=is%3Aopen+is%3Aissue+sort%3Acomments-desc https://github.com/issues?q=is%3Aopen+is%3Aissue+sort%3Acomm... https://github.com/peej/to.uri.st/issues/128 https://github.com/peej/to.uri.st/issues/128
- anrao_arao 10y agohttps://github.com/wting/autojump/issues/353 https://github.com/wting/autojump/issues/353 - 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!
- anrao_arao 10y agohttps://github.com/wting/autojump/issues/353 https://github.com/wting/autojump/issues/353 - 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!
- jbergknoff 10y agoWhy 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.
- floordaemon 10y agoThere is nothing at the URL specified. Its 404. What did we miss?
- tbolt 10y agoGot 11,995,200 problems but a repo aint one
- smpetrey 10y agoOn the other hand there's approximately 21 Million Closed Issues.
- dragthor 10y agoI wonder what the percentage is for "actual" issues? I see a lot of support & pilot error questions.
- schneems 10y agoA 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: https://www.codetriage.com https://www.codetriage.com
- NiftyFifty 10y agoI got 99 problems, but GitHub ain't one.