Skip to content

Labels

Labels

  • do-not-merge/release-note-label-needed

    Indicates that a PR should not merge because it's missing one of the release note labels.
  • do-not-merge/work-in-progress

    Indicates that a PR should not merge because it is a work in progress.
  • documentation

    Improvements or additions to documentation
  • 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.
  • jira/invalid-bug

    Indicates that a referenced Jira bug is invalid for the branch this PR is targeting.
  • jira/severity-critical

    Referenced Jira bug's severity is critical for the branch this PR is targeting.
  • jira/severity-important

    Referenced Jira bug's severity is important for the branch this PR is targeting.
  • jira/severity-informational

    Referenced Jira bug's severity is informational for the PR.
  • jira/severity-low

    Referenced Jira bug's severity is low for the branch this PR is targeting.
  • jira/severity-moderate

    Referenced Jira bug's severity is moderate for the branch this PR is targeting.
  • jira/valid-bug

    Indicates that a referenced Jira bug is valid for the branch this PR is targeting.
  • jira/valid-reference

    Indicates that this PR references a valid Jira ticket of any type.
  • 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/chore

    Categorizes issue or PR as related to maintenance and other usually non-code changes.
  • 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/deprecation

    Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
  • 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.
  • kind/regression

    Categorizes issue or PR as related to a regression from a prior release.
  • kind/support

    Categorizes issue or PR as a support question.
  • lgtm

    Indicates that a PR is ready to be merged.
  • lifecycle/active

    Indicates that an issue or PR is actively being worked on by a contributor.
  • lifecycle/frozen

    Indicates that an issue or PR should not be auto-closed due to staleness.
  • lifecycle/rotten

    Denotes an issue or PR that has aged beyond stale and will be auto-closed.