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.
Denotes a PR that is trusted and should be build.
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.
Further information is requested
Indicates an approved PR into a release branch has been approved by the release branch manager.
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 a PR is trusted, used by tide for auto-merging PRs.
Issues or PRs related to terraform.
Denotes an issue that blocks the tide merge queue for a branch while it is open.
Denotes a PR that should use a standard merge by tide when it merges.
Denotes a PR that should be rebased by tide when it merges.
Denotes a PR that should be squashed by tide when it merges.
This will not be worked on