Skip to content

No labels!

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

90 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
area/service-mesh
area/service-mesh
Issues or PRs related to service-mesh
area/support
area/support
Related to all activities around Kyma on-call
area/telemetry
area/telemetry
Issues or PRs related to the telemetry module
area/templates
area/templates
Issues or PRs related to templates
area/tests
area/tests
Issues or PRs related to tests
area/tooling
area/tooling
Issues or PRs related to tooling
area/tools/event-subscriber
area/tools/event-subscriber
Issues or PRs related to event-subscriber tool
area/tools/gitserver
area/tools/gitserver
Issues or PRs related to gitserver tool
area/tools
area/tools
Issues or PRs related to overall changes in tools
area/tracing
area/tracing
Issues or PRs related to the tracing module (deprecated)
auto-approved
auto-approved
Denotes a PR that was approved by automation.
cla: no
cla: no
Indicates the PR's author has not signed the CLA.
cla: yes
cla: yes
Indicates the PR's author has signed the CLA.
1
dependencies
dependencies
Pull requests that update a dependency file
do-not-merge/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
do-not-merge/invalid-commit-message
do-not-merge/invalid-commit-message
Indicates that a PR should not merge because it has an invalid commit message.
do-not-merge/invalid-owners-file
do-not-merge/invalid-owners-file
Indicates that a PR should not merge because it has an invalid OWNERS file in it.
do-not-merge/missing-docs-review
do-not-merge/missing-docs-review
Indicates that a PR should not merge beacuse it has missing documentation review.
do-not-merge/work-in-progress
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
documentation
documentation
Improvements or additions to documentation
duplicate
duplicate
This issue or pull request already exists
go
go
label for the "go" programming language
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
invalid
invalid
This doesn't seem right
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
kind/chore
kind/chore
Categorizes issue or PR as related to a chore.
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
kind/deprecation
kind/deprecation
Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
kind/failing-test
kind/failing-test
Categorizes issue or PR as related to a consistently or frequently failing test.