Shulou(Shulou.com)05/31 Report--

Most people do not understand the knowledge points of this article, "what is the use of kubernetes's Issue and PR tags?", so the editor summarizes the following, detailed contents, clear steps, and a certain reference value. I hope you can get something after reading this article. Let's take a look at this "what is the use of kubernetes's Issue and PR tags?"

General tag meaning Note good first issue indicates that the issue is suitable for new contributors to participate in the "help wanted" guidance document help wanted indicates that the issue needs help must meet the "help wanted" guidance document needs-kind indicates that the issue needs to specify a type tag

Lgtm indicates that the PR can be integrated.

A label that represents a type

Type tags are used to identify categories of Isuue or Pull Request, such as documents, bug, new features, technical liabilities, and so on. The label format that represents a type is kind/xxx (where xxx refers to a category).

The following table shows the labels commonly used in the community:

Tag meaning Note kind/design indicates that the issue is related to the design

Kind/documentation indicates that the issue is related to the document

Kind/feature indicates that the issue involves new features

Kind/cleanup indicates that the issue belongs to the type of code clean-up and technical liability

Kind/bug indicates that the issue involves bug

Kind/flake indicates that the issue is related to flaky test. It is possible that the kind/api-change reported by the Flake test indicates that the issue originated from the API change.

Kind/failing-test indicates that the issue is persistent or frequent

Needs-kind indicates that the PR is missing a type tag

Type tags can be used in Issue or Pull Request, but they are not required in Issue. On the contrary, if a Pull Request does not have any kind/xxx tags, the robot will automatically tag the Pull Request with a needs-kind tag to remind the reviewer of a certain type of tag.

In addition, kind/xxx tags are not mutually exclusive, which means that multiple kind/xxx tags can appear in the same Issue or Pull Request. For example, the same Pull Request may not only solve a bug but also do some code cleaning, so the Pull Request may have both kind/bug and kind/cleanup tags.

A label that represents a domain

The realm tag is used to identify the realm of Isuue or Pull Request, such as kubelet, etcd, kubectl, and so on. The tags that indicate the domain are all in area/xxx format.

There are many fields of Kubernetes, each of which needs a tag. Currently, there are more than 80 tags. In general, the field to which the tag belongs can be seen intuitively from the tag name. The commonly used tags are listed as follows:

Tag meaning remarks are/kubectlkubectl domain issues

Are/apiserverapiserver domain problem

Are/kubeletkubelet domain problem

A label that represents the amount of modification

Size/xxx is used to represent the amount of modification of a Pull Request so that reviewer can see the size of the modification visually.

After each Pull Request is created, the robot will tag the Pull Request with size/xxx according to the amount of code modification.

The number of modifications to each tag and its code are as follows: tag | description | remarks-|-|-size/XS | modify lines 0-9 | size/S | modify lines 10-29 | size/M | modify lines 30-99 | size/L | modify lines 100,499 | size/XL | modify lines 500,999 | size/XXL | modify more than 1000 lines |

The English definition of these sizes is the same as the clothing size:

S means trumpet, which stands for Small.

M means medium, which stands for Medium.

L means tuba, which stands for Large

Where X does not refer to a particular letter, but to the initial pronunciation of Extra, indicating something special:

XS means very small.

XL means very big.

XXL is bigger than XL.

There are two things to know:

The size/xxx tag applies only to Pull Request because Issue does not involve code modification

The size/xxx tag is automatically calculated and set by the robot without human intervention.

A label that indicates priority

Priority/xxx is used to identify the priority of Pull Request. The robot will first deal with the high-priority Pull Request and give priority to automatic testing.

The kubernetes community defines the following priorities:

Tag meaning Note priority/awaiting-more-evidence low priority, shelve for the time being

Priority/backlog General priority

Priority/important-longterm is important, but it takes a long period to complete.

Priority/important-soon is a high priority and should be dealt with as soon as possible.

Priority/critical-urgent highest priority

Needs-priority needs a priority label

When the Pull Request does not have a priority/xxx tag, the robot automatically marks it with a needs-priority tag, which means a priority tag is required.

The above is about the content of this article "what is the use of kubernetes's Issue and PR tags". I believe we all have a certain understanding. I hope the content shared by the editor will be helpful to you. If you want to know more about the relevant knowledge, please pay attention to the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.