Labels

• priority/p0

  priority/p0

  紧急：安全性问题、严重的 Bug 、导致阻塞的问题，每一分钟都会让我们损失钱。停下正在进行的一切直到这个问题解决。

• priority/p1

  priority/p1

  第二大优先级，应在 P0 优先级问题完成后立即开展工作，P1 级别的问题必须在下一个版本/迭代中解决。

• priority/p2

  priority/p2

  正常优先级：意味着「不错的选择」，默认的优先级别。

• priority/p3

  priority/p3

  最低的优先级，不要在有这个标签的 Issue/PR 上工作。根据需要，将在未来的冲刺阶段重新审视这些 issue/pr。

• shipped

  shipped

  The issue or pull request has been shipped.

• size/L

  size/L

  Denotes a PR that changes 100-499 lines.

• size/M

  size/M

  Denotes a PR that changes 30-99 lines.

• size/S

  size/S

  Denotes a PR that changes 10-29 lines.

• size/XL

  size/XL

  Denotes a PR that changes 500-999 lines.

• size/XS

  size/XS

  Denotes a PR that changes 0-9 lines.

• size/XXL

  size/XXL

  Denotes a PR that changes 1000+ lines.

• status/confirmed

  status/confirmed

  Confirmed: the issue or pull request is confirmed.

• status/delayed

  status/delayed

  Delayed: the issue or pull request is delayed.

• status/dont-merge

  status/dont-merge

  Don't merge: the issue or pull request is not ready to be merged.

• status/fixed

  status/fixed

  Fixed: the issue or pull request is fixed.

• status/implemented

  status/implemented

  Implemented: the issue or pull request is implemented.

• status/in-progress

  status/in-progress

  In progress: the issue or pull request is in progress.

• status/in-review

  status/in-review

  In review: the issue or pull request is in review.

• status/merge-conflicts

  status/merge-conflicts

  Merge conflicts: the issue or pull request has merge conflicts.

• status/need-review

  status/need-review

  Need review: the issue or pull request needs review.

• status/ready-to-merge

  status/ready-to-merge

  Ready to merge: the issue or pull request is ready to be merged.

• status/under-consideration

  status/under-consideration

  Under consideration: the issue or pull request is under consideration.

• status/wait-for-response

  status/wait-for-response

  Waiting for response: the issue or pull request is waiting for a response.

• time/1d

  time/1d

  1 day: the issue or pull request was estimate for 1 days.

• time/1h

  time/1h

  1 hour: the issue or pull request was estimate for 1 hours.

• time/25m

  time/25m

  25 minutes: the issue or pull request was estimate for 25 minutes.

• time/2h

  time/2h

  2 hours: the issue or pull request was estimate for 2 hours.

• time/4h

  time/4h

  4 hours: the issue or pull request was estimate for 4 hours.

• time/5m

  time/5m

  5 minutes: the issue or pull request was estimate for 5 minutes.

• type/breaking-change

  type/breaking-change

  Breaking change: the issue or pull request breaks a previously deployed version.