Labels

Issues or PRs that are questions around the project or a particular feature

Categorizes issue or PR as related to a security issue

Categorizes issue or PR as related to a TEP (or needs a TEP).

Indicates that a PR is ready to be merged.

Indicates a PR needs to be cherry-pick to a release branch

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.

Indicates a non-member PR verified by an org member that is safe to test.

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

Higher priority than priority/awaiting-more-evidence.

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.

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

Denotes a PR that introduces potentially breaking changes that require user action.

Denotes a PR that doesnt merit a release note.

Denotes a PR that changes 100-499 lines, ignoring generated files.

Denotes a PR that changes 30-99 lines, ignoring generated files.

Denotes a PR that changes 10-29 lines, ignoring generated files.

Denotes a PR that changes 500-999 lines, ignoring generated files.

Denotes a PR that changes 0-9 lines, ignoring generated files.

Denotes a PR that changes 1000+ lines, ignoring generated files.

Indicates an issue is a duplicate of other open issue.

Indicates an issue needs more information in order to work on it.

Indicates an issue that needs to be discussed during a working group call.

This will not be worked on