Labels

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 dependency changes.

Categorizes issue or PR as related to module or feature 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 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 related to technical debt.

Categorizes issue or PR as related to adding a test or fixing a failing test.

Categorizes issue or PR as related to a module or feature upgrade.

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

Categorizes issue or PR as related to upstream.

Indicates that a PR is ready to be merged.

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.

Indicates a PR that requires an org member to verify it is safe to test.

Indicates a PR cannot be merged because it has merge conflicts with HEAD.

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

Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Categorizes issue or PR as related to Clever.

Categorizes issue or PR as related to Compass.

Categorizes issue or PR that needs a product label.

Categorizes issue or PR as related to oem.

Further information is requested

Denotes a PR that will be considered when it comes time to generate release notes.