Search · zone

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 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 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 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 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.

34	Availability zones allow for the automatic and uniform distribution of units
35	across a region. A new instance, for example, will be allocated the zone
36	with the fewest members of its distribution group.
…
43	If you do not specify a zone explicitly, Juju will automatically and uniformly
44	distribute units across the available zones within the region. This can be

118	When bootstrapping, Juju contemplates three levels of placement: Cloud, Region and
119	Availability Zone. In vSphere, these are mapped in two different ways depending
120	on your topology:
121
122	- Cloud (vSphere endpoint), Region (data centre), Availability Zone (Host)

139	- DMZ space (with 2 subnets, one in each zone), hosting 2
140	units of the haproxy application, which is exposed and provides
…
142	- CMS space (also with 2 subnets, one per zone), hosting 2
143	units of mediawiki, accessible only via haproxy (not exposed).
144	- Database (again, 2 subnets, one per zone), hosting 2 units of

31	'vpc-juju-subnet'), select the VPC you created earlier, an Availability
32	Zone (optional), and an IPv4 CIDR block that resides within the initial
33	address space (e.g. '192.168.1.0/24').

203	arguments. Placement directives are provider specific. For example:
204
205	```bash
206	juju deploy mysql --to zone=us-east-1a
207	juju deploy mysql --to host.mass
208	```
209
210	The first example deploys to a specified zone for AWS. The second example

257	These exist for developmental purposes only.
258
259	#### JUJU_DUMMY_DELAY
260	#### JUJU_NOTEST_MONGOJS
261	#### JUJU_AVAILABILITY_ZONE

249	![List controller instance](./media/oracle_bootstrap-instances-2.png)
250
251	Oracle Compute has the notion of sites (like availability zone or region).
252	You may need to change your site to see your new controller. This is done in

89	* Gce invalid volume id destroying environment
90	Lp 1556293
91
92	* Juju_availability_zone not set in maas
…
290	You can list all the subnets known by Juju and optionally filtering them by
291	space and/or availability zone like so:
292
293	juju subnet list [--zone <name>] [--space <name>] [<zone1> <zone2> …]

261	juju add-machine zone=us-east-1a (start a machine in zone us-east-1a on AWS)
262	juju add-machine maas2.name (acquire machine maas2.name on MAAS)
…
603	since any subnet needs to be part of at least one zone, specifying
604	zone(s) is required.
605
606
607
608
609	^# add-unit
610
611	Usage: ` juju add-unit [options] <application name>`