Things I would build if I worked at GitHub

Re:Things I would build if I worked at GitHub by danielsamuels on Wednesday August 05, 2015 @04:44PM (#10012723)

I've gotta say, I strongly disagree with this:

> GitHub already has a great code search

At some point in the last year or so Github rolled out a new search engine which drastically reduced it's usefulness. Any moderately complex search query now has all of the modifiers and key bits stripped out making your search results unnecessarily cluttered and somewhat useless. I consider it to be one of the worst parts of the site these days.

[ Parent | on HN ]

Re:Things I would build if I worked at GitHub by davidcelis on Wednesday August 05, 2015 @05:35PM (#10013032)

I really wish there were some way to run code searches against branches/commits that aren't HEAD. If there is, it's not obvious.

[ Parent | on HN ]

Re:Things I would build if I worked at GitHub by jberryman on Wednesday August 05, 2015 @05:43PM (#10013084)

I regret every single time I try to use github search, even for the most basic "where is X defined" type queries.

[ Parent | on HN ]

Re:Things I would build if I worked at GitHub by justinhj on Wednesday August 05, 2015 @11:46PM (#10014424)

Git grep is really fantastic, if github search came close I'd be delighted

[ Parent | on HN ]

Re:Things I would build if I worked at GitHub by p8952 on Thursday August 06, 2015 @05:25AM (#10015392)

Could you please elaborate on what parts of git-grep you find most useful?

[ Parent | on HN ]

Re:Things I would build if I worked at GitHub by anshukla on Wednesday August 05, 2015 @11:43PM (#10014415)

Depending on what you're trying to search for, maybe something intelligent like Sourcegraph would work?

[ Parent | on HN ]

Re:Things I would build if I worked at GitHub by johnbellone on Thursday August 06, 2015 @06:31AM (#10015600)

GitHub has horrible search.

[ Parent | on HN ]