Skip to content

No labels!

There aren’t any labels for this repository quite yet.

79 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
invalid
invalid
Investigation
Investigation
javascript
javascript
Pull requests that update Javascript code
11
kind/api-change
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
4
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
kind/dependency
kind/dependency
Categorizes issue or PR as related to dependency changes.
kind/deprecation
kind/deprecation
Categorizes issue or PR as related to module or feature deprecation.
kind/design
kind/design
Categorizes issue or PR as related to design.
kind/documentation
kind/documentation
Categorizes issue or PR as related to documentation.
kind/enhancement
kind/enhancement
Categorizes issue or PR as related to enhancement.
kind/feature
kind/feature
Categorizes issue or PR as related to a new feature.
9
kind/flake
kind/flake
Categorizes issue or PR as related to a flaky test.
kind/new-api
kind/new-api
Categorizes issue or PR as related to new api.
kind/proposal
kind/proposal
Proposing Changes to Cyclone
1
kind/question
kind/question
kind/regression
kind/regression
Categorizes issue or PR as related to a regression from a prior release.
kind/support
kind/support
Categorizes issue or PR as related to support.
kind/technical-debt
kind/technical-debt
Categorizes issue or PR as related to technical debt.
kind/test
kind/test
Categorizes issue or PR as related to adding a test or fixing a failing test.
kind/upgrade
kind/upgrade
Categorizes issue or PR as related to a module or feature upgrade.
kind/upgrade-test-failure
kind/upgrade-test-failure
Categorizes issue or PR as related to a consistently or frequently failing test.
kind/upstream
kind/upstream
Categorizes issue or PR as related to upstream.
lgtm
lgtm
Indicates that a PR is ready to be merged.
lifecycle/frozen
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
lifecycle/rotten
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
lifecycle/stale
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
needs-ok-to-test
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
needs-rebase
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.