Labels

• approval/approved

  Indicates a PR has been approved by an approver from all required owners.
• approval/lgtm

  Indicates a PR is ready to be merged.
• approval/ok-to-test

  Indicates a non-member PR verified by an org member that is safe to test.
• area/agent

  Categorizes an issue or PR as related to Upwind Agent.
• area/cli

  Categorizes an issue or PR as related to Upwind CLI.
• area/dependency

  Categorizes an issue or PR as related to dependency changes.
• area/github

  Categorizes an issue or PR as related to GitHub.
• area/helm

  Categorizes an issue or PR as related to Upwind Helm charts.
• area/infra

  Categorizes an issue or PR as related to infrastructure.
• area/licensing

  Categorizes an issue or PR as related to licensing.
• do-not-merge/blocked-paths

  Indicates a PR should not merge because it touches files in blocked paths.
• do-not-merge/hold

  Indicates a PR should not merge because someone has issued a /hold command.
• do-not-merge/invalid-commit-message

  Indicates a PR should not merge because it has an invalid commit message.
• do-not-merge/work-in-progress

  Indicates a PR should not merge because it is a work in progress.
• kind/api-change

  Categorizes an issue or PR as related to adding, removing, or otherwise changing an API.
• kind/bug

  Categorizes an issue or PR as related to a bug.
• kind/build

  Categorizes an issue or PR as related to the build configuration.
• kind/cleanup

  Categorizes an issue or PR as related to cleaning up code, process, or technical debt.
• kind/deprecation

  Categorizes an issue or PR as related to a feature/enhancement marked for deprecation.
• kind/documentation

  Categorizes an issue or PR as related to documentation.
• kind/explore

  Categorizes an issue or PR as related to ideas worth exploring for future.
• kind/feature

  Categorizes an issue or PR as related to a new feature or request.
• kind/regression

  Categorizes an issue or PR as related to a regression from a prior release.
• kind/release

  Categorizes a PR as related to a release (version bump, changelog, etc.).
• kind/support

  Categorizes an issue or PR as related to a support request.
• lifecycle/active

  Indicates an issue or PR is actively being worked on by a contributor.
• lifecycle/automated

  Indicates this PR was automatically generated (could be used for bots or scheduled tasks).
• lifecycle/frozen

  Indicates an issue or PR should not be auto-closed due to staleness.
• lifecycle/rotten

  Indicates an issue or PR has aged beyond stale and will be auto-closed.
• lifecycle/stale

  Indicates an issue or PR has remained open with no activity and has become stale.