Pull requests that update Go code
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
Pull requests that update Javascript code
Categorizes issue or PR as related to a bug.
Categorizes issue or PR as related to a chore.
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 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 missing automated tests for scenario.
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.
Used to keep track of any scenarios that can cause non-recoverable outages.
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.
Pull requests that update Python code