Labels

Indicates that a PR should not merge because it has an invalid OWNERS file in it.

Indicates a PR lacks a `kind/foo` label and requires one.

Indicates an issue or PR lacks a `sig/foo` label and requires one.

Indicates that a PR should not merge because it's missing one of the release note labels.

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

New feature or request

Pull requests that update GitHub Actions code

gitlink2024

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

ospp2024

Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

This doesn't seem right

Pull requests that update javascript code

Categorizes issue or PR as related to adding, removing, or otherwise changing an API

Categorizes issue or PR as related to a bug.

Categorizes issue or PR as related to cleaning up code, process, or technical debt.

Categorizes issue or PR as related to a feature/enhancement marked for deprecation.

Categorizes issue or PR as related to design.

Categorizes issue or PR as related to documentation.

Categorizes issue or PR as related to a consistently or frequently failing test.

Categorizes issue or PR as related to a new feature.

Categorizes issue or PR as related to a flaky test.

Categorizes issue or PR as related to a regression from a prior release.

Categorizes issue or PR as a support question.

"Looks good to me", indicates that a PR is ready to be merged.

Indicates that an issue or PR is actively being worked on by a contributor.

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

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

Denotes an issue or PR has remained open with no activity and has become stale.