It seems to work with @{any letter}. Can anybody explain to me how GitHub is interpreting this search term?
Find out how many users/repos Github has by a simple search
21–30 of 30 posts
Re: Find out how many users/repos Github has by a simple search
#22Re: Find out how many users/repos Github has by a simple search
#23"@defunkt Get all repositories from the user defunkt."
Seeing as there _is_ a user called "a: (http://github.com/a) but he doesn't have a single line of code, no repositories and no active issues either; the search breaks somehow and returns the repository, issue and code (LOC?) count of ALL people.
For example trying it with "@b" (or any existing user after the at-sign) does yield the correct results (the respective counts for user b: http://github.com/b). Trying it with someone with no repositories, code and issues OR a user which does not exist (@thisuserdoesnotexist) results in the same behavior.
Re: Find out how many users/repos Github has by a simple search
#24So now you could scrape the name of every GitHub user and their email if it is public.
https://api.github.com/users?since=0
And iterate on. They even give you a HTTP header for the next URI:
Link: ;" rel="nofollow">https://api.github.com/users?since=135>; rel="next"
There is a rate limit of 60 (per hour), but if you use oauth then it's 5000. See http://developer.github.com/v3/#rate-limiting
Re: Find out how many users/repos Github has by a simple search
#25Sorting by "Least recently joined" is interesting. The GitHub team are all there, naturally, but I'm intrigued what "tater" is about. Yehuda Katz is famously user ID 4 but tater shows up as user 611789 through the API. Other than that, the first 10 pages or so are a real who's who of the Ruby scene in 2007-2008 :-)
Back then you pretty much had to be invited by a Ruby/Rails person. I got in by submitting a patch to Dr Nic. :)
Re: Find out how many users/repos Github has by a simple search
#26Search more than 4.3M Users
Search more than 8.8M Repositories
Search more than 18.7M Issues
Re: Find out how many users/repos Github has by a simple search
#27So how does this work? From the search its cheat sheet: "@defunkt Get all repositories from the user defunkt." Seeing as there _is_ a user called "a: ( http://github.com/a ) but he doesn't have a single line of code, no repositories and no active issues either; the search breaks somehow and returns the repository, issue and code (LOC?) count of ALL people. For example trying it with "@b" (or any existing user after t…
[edit 1] @everybody seems to return every user
[edit 2] @everything seems to return ... everything.
[edit 3] @qdfhsdfjsdqjrekle seems to return everything. Ok. It's a bug. :>
Re: Find out how many users/repos Github has by a simple search
#28So how does this work? From the search its cheat sheet: "@defunkt Get all repositories from the user defunkt." Seeing as there _is_ a user called "a: ( http://github.com/a ) but he doesn't have a single line of code, no repositories and no active issues either; the search breaks somehow and returns the repository, issue and code (LOC?) count of ALL people. For example trying it with "@b" (or any existing user after t…
@a is probably an alias for @all ( https://github.com/search?q=%40all&type=Users&ref=searchresu... ). [edit 1] @everybody seems to return every user [edit 2] @everything seems to return ... everything. [edit 3] @qdfhsdfjsdqjrekle seems to return everything. Ok. It's a bug. :>
Re: Find out how many users/repos Github has by a simple search
#29It seems to work with @{any letter}. Can anybody explain to me how GitHub is interpreting this search term?
Re: Find out how many users/repos Github has by a simple search
#30Sorting by "Least recently joined" is interesting. The GitHub team are all there, naturally, but I'm intrigued what "tater" is about. Yehuda Katz is famously user ID 4 but tater shows up as user 611789 through the API. Other than that, the first 10 pages or so are a real who's who of the Ruby scene in 2007-2008 :-)
Woop. 140th person to join GitHub. Back then you pretty much had to be invited by a Ruby/Rails person. I got in by submitting a patch to Dr Nic. :)