Advanced search
Cheat sheet

Search cheat sheet

GitHub’s search supports a variety of different operations. Here’s a quick cheat sheet for some of the common searches.

For more information, visit our search help section.

Basic search

This search Finds repositories with…
cat stars:>100 Find cat repositories with greater than 100 stars.
user:defunkt Get all repositories from the user defunkt.
tom location:"San Francisco, CA" Find all tom users in "San Francisco, CA".
join extension:coffee Find all instances of join in code with coffee extension.
NOT cat Excludes all results containing cat.

Repository search

Repository search looks through the projects you have access to on GitHub. You can also filter the results:

This search Finds repositories with…
cat stars:>100 Find cat repositories with greater than 100 stars.
user:defunkt Get all repositories from the user defunkt.
pugs pushed:>2013-01-28 Pugs repositories pushed to since Jan 28, 2013.
node.js forks:<200 Find all node.js repositories with less than 200 forks.
jquery size:1024..4089 Find jquery repositories between the sizes 1024 and 4089 kB.
gitx fork:true Repository search includes forks of gitx.
gitx fork:only Repository search returns only forks of gitx.

Code search

Code search looks through the files hosted on GitHub. You can also filter the results:

This search Finds repositories with…
install repo:charles/privaterepo Find all instances of install in code from the repository charles/privaterepo.
shogun user:heroku Find references to shogun from all public heroku repositories.
join extension:coffee Find all instances of join in code with coffee extension.
system size:>1000 Find all instances of system in code of file size greater than 1000kbs.
examples path:/docs/ Find all examples in the path /docs/.
replace fork:true Search replace in the source code of forks.

Issue search

Issue search looks through issues and pull requests on GitHub. You can also filter the results:

This search Finds issues…
encoding user:heroku Encoding issues across the Heroku organization.
cat is:open Find cat issues that are open.
strange comments:>42 Issues with more than 42 comments.
hard label:bug Hard issues labeled as a bug.
author:mojombo All issues authored by mojombo.
mentions:tpope All issues mentioning tpope.
assignee:rtomayko All issues assigned to rtomayko.
exception created:>2012-12-31 Created since the beginning of 2013.
exception updated:<2013-01-01 Last updated before 2013.

User search

User search finds users with an account on GitHub. You can also filter the results:

This search Finds repositories with…
fullname:"Linus Torvalds" Find users with the full name "Linus Torvalds".
tom location:"San Francisco, CA" Find all tom users in "San Francisco, CA".
chris followers:100..200 Find all chris users with followers between 100 and 200.
ryan repos:>10 Find all ryan users with more than 10 repositories.

tidy up some correctness issues reported by go vet

I use go vet (http://golang.org/cmd/go/#hdr-Run_go_tool_vet_on_packages) as a presubmit hook on almost all of my go code. It definitely helps with finding correctness problems.

  • Opened by andybons Feb 14, 2014
  • 3 comments
#1

add pre-commit hook & convenience script to add it. fix some vet errors.

The precommit will run - go vet - all package tests - gofmt Within the cockroach dir, just run the initrepo.sh script and it will be enabled for you.

  • Opened by andybons Feb 14, 2014
  • 12 comments
#2

fix golint reports

With the exception of the renaming of MIN_GROUP and MAX_GROUP this is almost completely comment changes that will put us within the stylistic goodwill of golint. There were some other things I wanted ...

#3

Added diff of an InfoStore with a supplied Filter

Diffs determine approximate difference in number of keys known by the builder of the Filter but unknown to the InfoStore. It's an heuristic for how good of a gossip peer the builder of the Filter would ...

#4

Add field names to composite literals

While more verbose, composite literals with explicit field names are a good idea because: - Bugs (sometimes very subtle) can arise simply by changing the order of fields in a struct type declaration. ...

  • Opened by andybons Feb 15, 2014
  • 3 comments
#5

Shawn/protobuf

@spencerkimball

#7

add myself to AUTHORS

Wasn’t sure what the difference was between original authors and partial contributors. Since I wasn’t a part of the initial design doc discussion, putting myself in the partial list.

  • Opened by andybons Feb 16, 2014
  • 1 comment
#8

reduce visibility of hasher and filter

also updates field comments to be idiomatic, albeit more verbose.

  • Opened by andybons Feb 16, 2014
  • 3 comments
#9