StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Update of the Update (February 2013, source "<strong><a href="https://github.com/blog/1410-sortable-stars" rel="nofollow noreferrer">Sortable Stars</a></strong>"):</p> <blockquote> <p>Starting today you can sort your <a href="https://github.com/stars" rel="nofollow noreferrer">starred repositories</a> by when you starred them or when the repositories were last updated. </p> </blockquote> <p><img src="https://i.stack.imgur.com/YkD3b.gif" alt="enter image description here"></p> <p>So the sort criteria is now visible.</p> <hr> <p>Update January 2013 (source: "<a href="https://github.com/blog/1381-a-whole-new-code-search" rel="nofollow noreferrer"><strong>A whole new code search</strong></a>")</p> <p>Searching by number of forks seems now to return a result ordered by number of forks</p> <p><a href="https://github.com/search?q=django-%20forks:%3E500&type=Repositories&ref=advsearch&l=" rel="nofollow noreferrer"><code>django- forks:>500</code></a></p> <p>This is confirmed by the blog post "<a href="https://github.com/blog/1396-sorting-through-search-results" rel="nofollow noreferrer">Sorting through Search Results</a>" (January 31, 2013):</p> <blockquote> <p>If you're searching through repositories, you can sort by stars, forks, or recently-updated</p> </blockquote> <hr> <p>(Original answer: Sept. 2012)</p> <p>I don't see any sort option in GitHub advanced search.</p> <p>The forks: filter is to indicate a precise number of fork, like <a href="https://github.com/search?q=django-%20forks:100%20fork:&repo=&langOverride=&start_value=1&type=Repositories&language=" rel="nofollow noreferrer">this query</a> would display the 4 repos with 100 forks for "<code>django-</code>". But that doesn't display <em>all</em> repo above 100 forks, and that doesn't sort them.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload