Skip to content
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.

5 commit results in untangle/ngfw_src or view all results on GitHub

          On upgrade to v16.0 we want to clear the passwordHashBase64
field for the admin user.  From this point on we will prefer to
authenticate admin users using the passwordHashShadow field
which was generated from a much stronger hash.  Because of
the changes made in 16.0, simply calling setSettings will do
the clearing of the passwordHashBase64 field for any user
the has the passwordHashShadow field set.

NGFW-13198
        
Brett Mastbergen committed Aug 10, 2020
          If a user has passwordHaseBase64 defined, change the 'Change Password'
icon and tooltip to suggest the user change the users password immediately

NGFW-13198
        
Brett Mastbergen committed Aug 10, 2020
          If there are any admin users with a non-empty passwordHashBase64 field
add a notification suggesting that they update those users' passwords
immediately.  Include a link to Config->Administration->Admin.

NGFW-13198
        
Brett Mastbergen committed Aug 10, 2020
          When a new admin user is created, or when the password for an
existing admin user is changed, generate the passwordHashShadow
instead of passwordHashBase64.  Furthermore, for admin users
that have passwordHashShadow defined, return "" for
passwordHashBase64, effectively clearing it in the settings file

NGFW-13198
        
Brett Mastbergen committed Aug 10, 2020
          If the stronger passwordHashShadow is defined for an admin user, use
that to authenticate.  But, fall back to using the older, weaker hash
if the stronger shadow hash isn't defined for the particular user.

NGFW-13198
        
Brett Mastbergen committed Aug 10, 2020