Labels

• 0.3-alpha-0 blocker
• cherry-pick-approved

  Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
• cherry-pick/release-0.3

  This PR should be cherry-picked to release-0.3 branch.
• cherry-pick/release-0.4

  This PR should be cherry-picked to release-0.4 branch.
• cherry-pick/release-0.5

  This PR should be cherry-picked to release-0.5 branch.
• cherry-pick/release-0.6

  This PR should be cherry-picked to release-0.6 branch
• cherry-pick/release-0.7

  This PR should be cherry-picked to release-0.7 branch
• cherry-pick/release-0.8

  This PR should be cherry-picked to release-0.8 branch
• documentation

  Improvements or additions to documentation
• engine
• 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.
• kind/api-change

  Categorizes issue or PR as related to adding, removing, or otherwise changing an API
• kind/bug

  Categorizes issue or PR as related to a bug.
• kind/cleanup

  Categorizes issue or PR as related to cleaning up code, process, or technical debt.
• kind/dependency-change

  Categorizes issue or PR as related to changing dependencies
• kind/design

  Categorizes issue or PR as related to design.
• kind/documentation

  Categorizes issue or PR as related to documentation.
• kind/failing-test

  Categorizes issue or PR as related to a consistently or frequently failing test.
• kind/feature

  Categorizes issue or PR as related to a new feature.
• kind/flake

  Categorizes issue or PR as related to a flaky test.
• needs-kind

  Indicates an issue or PR lacks a `kind/foo` label and requires one.
• needs-priority

  Indicates an issue or PR lacks a `priority/foo` label and requires one.
• needs-rebase

  Indicates a PR cannot be merged because it has merge conflicts with HEAD.
• needs-triage

  Indicates an issue or PR lacks a `triage/foo` label and requires one.
• parity
• performance

  Analyzer performance related issues
• priority/awaiting-more-evidence

  Lowest priority. Possibly useful, but not yet enough support to actually get it done.
• priority/backlog

  Higher priority than priority/awaiting-more-evidence.
• priority/critical-urgent

  Highest priority. Must be actively worked on as someone's top priority right now.