Welcome to my GitHub

https://github.com/zq2599/blog_demos

Content: all the original article classification summary and supporting source code, involving Java, Docker, Kubernetes, DevOps and so on;

On search

  • For myself, this is an important note late. GitHub is a treasure house, and improper search methods may pass by precious codes. Therefore, I classify and summarize the commonly used search methods for emergency needs.
  • < FONT color=”blue”>

  • Although search is more commonly used, the principle is to start with author search first.

The author search

  • fullname >

  • fullname:

  • Many GitHub accounts set their own addresses, as shown in the red box below, which can also be used as a condition for finding someone:

  • Tom , there will be a number of names:

  • fullname: Tom location: Shenzhen

  • That’s how you search for a user, followed by the more common content search;

Content search overview

  • There are a few more parameters when searching content. According to usage habits, I simply divide them into three categories:
  • Accurate: The format is language: full keywords , such as language: Java
  • in: condition name keyword , e.g. in:name spring-boot
  • condition name :> number , often used with other conditions, such as in:name spring-boot stars:>10000
  • The three types of search mentioned above are discussed in detail;

accurate

  • Specifies the language most commonly used accurate search type, see not specified language types, first search < font color = “blue” > breakpoint continuingly < / font > the result of the following figure, all kinds of languages have:

  • > > > >

The fuzzy

  • Ambiguity is the key to locking content, and there are three commonly used criteria: name (project name), description (project description), and readme (read.md file in the repository).
  • in:name spring boot.

  • For example, if I want to find an existing breakpoint continuation code, the Java version, the search condition is in:description breakpoint continuation language: Java

  • It is also very common to search the contents of readme. md in the repository, which usually contains detailed documentation information. For example, I think the server side code of GRPC, the Java version, in:readme GRPC Server Language: Java

  • in:readme kubernetes >

    And:

The scope of

  • You can also specify a range if the previous method is used to search too much. The usual types are: stars (number of stars), forks (number of forks), pushed (last submission time), and size (file size)
  • in:name spring-boot stars:>10000

  • in:name spring-boot forks:>10000

  • Items with spring-boot in search name and updated after March 12, 2021 in:name spring-boot :>2021-03-12

  • in:name spring-boot size:>100, in:name spring-boot size:>100, Note that the default unit for this number is k :

The sorting

  • After searching the results, you can also adjust the sorting of the results. The operation position is shown in the red box below:

List each sort type in the red box above:

The name of the meaning
Best match Keyword matching degree
Most stars Most star
Fewest stars A minimum of star,
Most forks Up to the fork
Fewest forks At least the fork
Recently updated Recent updates
Least recently updateed The most recent update date
  • The above is a summary of my GitHub search skills, I hope to give you some reference, more efficient discovery of GitHub treasures;

You are not alone, Xin Chen original all the way

  1. Java series
  2. Spring series
  3. The Docker series
  4. Kubernetes series
  5. Database + middleware series
  6. The conversation series

Welcome to pay attention to the public number: programmer Xin Chen

WeChat search “programmer Xin Chen”, I am Xin Chen, looking forward to traveling with you in the JAVA world…


https://github.com/zq2599/blog_demos