Hardcore! How accurate search for open source projects in Github?

Many small partners, often have such confusion, I read a lot of technical study documents, books, and even video, I'd like to hands-on, so I turned on GitHub, trying to find a open source project, learn, get hands-on experience project . This time many small partners will be faced with the question: "I will not search ah, how can I Zhaoya?", We can only give up.

I believe after reading this article, you can learn how to accurately search project on GitHub.

Part of open source projects

Before it clear, let's first look at a part of what open source projects are:

  • name: Project name

  • A brief description of the project: description

  • The project source code

  • Details of the project are: README.md

Then in addition to these factors, star number and the number of fork the project itself, but also judge whether an open source project fiery standard, which is also a very important search criteria. In addition, we also observe Last update of this project, because the more active project, its modified date is also more frequent.

Some of the key elements of the above point is that when we are conducting a search should be noted.

How to Search

That we are in the end how to search for it?

Suppose we now want to search React, I believe most are small partner directly in the search box enter: "React", then a carriage return, you will find the situation like this:

Search results will show a lot of open source projects, just to let you overwhelmed, unable to start, many small partner search to this step to give up, because the project too much, could not find how to find open source projects they are interested in, so this Search is very inaccurate. So let's learn a little about the precise point search method.

Search by name

React to search for items which contains the name of the project:

in:name React  

Results are as follows:

You can see, these are the search results Project name inside with "React" keyword, but the number of projects is still a lot.

Now let's look at the constraints

For example, I would be accurate to a few star items is greater than 5000 +:

in:name React stars:>5000  

The result is this:

Search Results precise moment a lot, now only 114 items to choose from. Of course, we generally do not set the number of the star so high, generally set a 1000 on the same subject.

Similarly, we can also search by the number of fork:

in:name React stars:>5000 forks:>3000  

You will find that more and more accurate results!

According to README to search

Search README.md which contains React items:

in:readme React

The results have so many, so we'll limit what its star number and fork number:

in:readme React stars:>3000 forks:>3000

Search results are accurate to 90 at once. This time you go to select an item, it will become much easier.

Search by descriptin

Suppose we now want to study micro-project service, we search project description (description) which contains micro-services projects:

in:description 微服务

There are so many results, we then add some filtering criteria:

in:description 微服务 language:python

language: python mean we limit the language to python, let's see what happens:

Search results precise a lot.

If these items inside, we want to find project was recently updated, meaning that in the last update time, we can:

in:description 微服务 language:python pushed:>2020-01-01

pushed:> 2020-01-01 mean we last updated the project limits to 2020-01-01, we look at how the results:

Only eight of the search results, these projects belong to update more active project, under which no longer tangled up.

to sum up

Well, let's sum up. We want to be accurate search, nothing more than increase the filter criteria.

  • in: name xxx // Search by project name

  • in: readme xxx // in the README search

  • in: description xxx // search according to description

So in this inside it, we can increase Filters

  • stars:> xxx // xxx is greater than the number of stars

  • forks:> 3000 // xxx is greater than the number of forks

  • language: xxx // programming language is xxx

  • pushed:> YYYY-MM-DD // last update time is greater than YYYY-MM-DD

These are some tips we have accurate search project on GitHub above, I hope for your help!

Author: Juefei
juejin.im/post/5e3d01c56fb9a07c91100801

Recommended to my blog to read more

1. the Java the JVM, collections, multithreading, new series of tutorials

2. the Spring MVC, the Boot the Spring, the Spring series of tutorials Cloud

3. Maven, Git, the Eclipse, IDEA Intellij Tool Tutorial Series

4. the Java, the back-end architecture, Alibaba and other manufacturers face new questions

Life is beautiful, see tomorrow ~

Guess you like

Origin www.cnblogs.com/javastack/p/12454297.html