Many small partners often have this kind of confusion. I read a lot of technical learning documents, books, and even videos, and I wanted to practice them. So I opened GitHub to find an open source project to learn and gain practical experience. When I was a child, I would not find a partner like this In the end, we can only give up.
I believe that after reading this article, you can learn how to accurately search for items in GitHub.
Components of open source projects
Before we make it clear, let’s first understand the components of an open source project
- Name: project name
- Description: a brief description of the project
- Source code of the project
- README.md Introduction to the details of the project
Besides these criteria, forstar is also an important factor to judge whether a project is hot or not. In addition, we should also pay attention to the latest update date of the project, because the more active the project is, the more frequent the update date is.
Some of the key points we should pay attention to when we search.
How to search
So how do we search?
Suppose we want to search react now. I believe most of our little friends directly type “react” in the search box, and then as soon as you enter, you will find that the situation is like this:
The search results will show a lot of open source projects, which makes you overwhelmed and unable to start. Many small partners give up when they find this step. Because there are too many projects, they don’t know how to find the open source projects they are interested in, so the search is very inaccurate. So let’s learn a slightly more accurate search method.
Search by name
The search item name contains react items:
in:name ReactThe results are as follows
As you can see, these search results are all items with the “react” keyword in the item name, but the number of items is still large.
Now let’s restrict it
For example, I can get the number of stars more than 5000 +:
in:name React stars:>5000The result is this:The search results are much more accurate in an instant. Now there are only 114 items to choose from. Of course, we usually don’t set the star number so high. Generally, it’s about 1000.
Similarly, we can search by the number of forks:
in:name React stars:>5000 forks:>3000
You will find that the results are more and more accurate!
Search according to readme
search README.md It contains react projects:
in:readme ReactThere are so many results. Let’s limit the star number and fork number
in:readme React stars:>3000 forks:>3000
All of a sudden, the search results are accurate to 90. At this time, it will be much easier for you to choose projects.
Search by descriptin
Suppose we want to learn about microservice items now. We search the item description for microservice items
In: description microservice
There are so many results. Let’s add some screening conditions
Description: in service language:pythonlanguage:python We limit the language to python. Let’s see how it turns out
The search results are much more accurate.
If in these projects, we want to find the latest updated project, which means that the update time is the latest, we can do this:
Description: in service language:python pushed:>2020-01-01Pushed: > 2020-01-01 means that we limit the final update time of the project to after 2020-01-01. Let’s see the result
There are only 8 search results. These items belong to the more active items, which will not be tangled any more.
summary
OK, let’s summarize. If we want to conduct accurate search, we just need to increase the screening criteria
In: name XXX / / search by item nameIn this case, we can add the screening conditions:
Stars: > XXX / / the number of stars is greater than XXXThe above are some tips for us to accurately search for items on GitHub, hoping to help you!
Author: Jue Fei
Link:https://juejin.im/post/5e3d01…
