If those searches had uncovered no passwords whatsoever - now that would be surprising. This is just what would be expected - just by sheer chance. And yes - it is Github's responsibility to protect its users from their own stupidity.
Github's sole value is in its community - any of the technical issues that they have to deal with are commodity and have already been dealt with before else where. Github's net worth is in its community good will and path dependence.
Killing search for now is the right decision to keep the gravy train running.
"Poor software engineering practices lead to exposed vulnerabilities again"
Or: "Hackers use Github to launch destructive attack on tech companies' databases"?
That kind of headline would make it especially hard for code teams to convince corporate IT to let them have a github account, even for private repos.
Github did the most sensible thing...it's too hard to come up with a provably effective filter that prevents the compromise of inadvertently exposed data.
I'd argue it's not, but the issue creates such bad PR that it'd be prudent for them to add some sort of check. However, it should probably be a bit more nuanced than killing search :)