Labels

• ansible

  Categorizes issue as related to tidb-ansible
• approved
• area/ticdc
• category/document

  Categorizes issue or PR as a document update.
• category/monitoring

  Categorizes issue or PR related to monitoring components.
• category/security

  Categorizes issue or PR as a security enhancement.
• category/stability

  Categorizes issue or PR as a stability enhancement.
• category/testing

  Categorizes issue or PR as a testing enhancement.
• category/usability

  Categorizes issue or PR as a usability enhancement.
• component/bench

  Issues about the tiup-bench component
• component/client

  Issues about the tiup-client component
• component/cluster

  Issues about the tiup-cluster component
• component/ctl

  Issues about the ctl component in TiUP
• component/dm

  Issues about the tiup-dm component
• component/doc

  Issues about the doc and errdoc components
• component/playground

  Issues about the tiup-playground component
• component/tiup

  Issues about the TiUP package management component itself
• difficulty/easy

  Indicates that a issue is easy to resolve.
• difficulty/hard

  Indicates that a issue is hard to resolve.
• difficulty/medium

  Indicates that a issue is medium to resolve.
• do-not-merge/hold

  Indicates that a PR should not merge because someone has issued a /hold command.
• do-not-merge/work-in-progress

  Indicates that a PR should not merge because it is a work in progress.
• first-time-contributor
• good first issue

  Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
• help wanted

  Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
• invalid
• lgtm
• needs-rebase

  Indicates a PR cannot be merged because it has merge conflicts with HEAD.
• priority/P0

  Indicates that the priority of a issue is very high.
• priority/P1

  Indicates that the priority of a issue is high.