Categorizes issue or PR as related to a regression from a prior release.
Denotes an issue that has been triaged and determined to be valid.
Indicates that an issue or PR should not be auto-closed due to staleness.
Denotes an issue that is assigned and is being actively investigated by the issue owner.
Denotes an issue or PR has remained open with no activity and has become stale.
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 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.
This will not be worked on