Issues or PRs related to service management
Issues or PRs related to service-mesh
Related to all activities around Kyma on-call
Issues or PRs related to the telemetry module
Issues or PRs related to templates
Issues or PRs related to tests
Issues or PRs related to tooling
Issues or PRs related to event-subscriber tool
Issues or PRs related to gitserver tool
Issues or PRs related to overall changes in tools
Issues or PRs related to the tracing module (deprecated)
Denotes a PR that was approved by automation.
Indicates that a PR should not merge because someone has issued a /hold command.
Indicates that a PR should not merge because it has an invalid commit message.
Indicates that a PR should not merge because it has an invalid OWNERS file in it.
Indicates that a PR should not merge beacuse it has missing documentation review.
Indicates that a PR should not merge because it is a work in progress.
Improvements or additions to documentation
This issue or pull request already exists
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.
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.