Labels

• Area: Cross-product

  Legal, governance, CODEOWNERS, or work spanning multiple product paths.
• Area: Kubernetes operators

  Kubernetes operators platform messaging (products/operators/).
• Area: MongoDB

  MongoDB ecosystem messaging (products/mongodb/).
• Area: MySQL

  MySQL ecosystem messaging (products/mysql/ and MySQL-scoped operator lines).
• Area: PMM

  Percona Monitoring and Management messaging (products/pmm/).
• Area: PostgreSQL

  PostgreSQL ecosystem messaging (products/postgresql/).
• Area: Valkey/Redis

  Valkey and Redis ecosystem messaging (products/valkey-redis/).
• Automation & CI

  CI workflows, scripts, maps under automation/, and tooling.
• bug

  Something isn't working
• Content & messaging

  Canonical copy, products, use cases, case studies, and narrative.
• dependencies

  Pull requests that update a dependency file
• Downstream

  Outbound: repo canon changed; templates, datasheets, docs, web, or other surfaces need follow-up.
• duplicate

  This issue or pull request already exists
• enhancement

  New feature or request
• Feature / build

  New capability: build it, ship it, or add a new check.
• github_actions

  Pull requests that update GitHub Actions code
• Go-live & repo setup

  Before public: labels, branch protection, CODEOWNERS, hosting, read site, visibility.
• good first issue

  Good for newcomers
• Governance & policy

  Rules, review expectations, legal/compliance, naming, and editor rules alignment.
• help wanted

  Extra attention is needed
• Inbound

  Inbound: ships, GTM, or external requests driving updates to canonical messaging in this repo.
• invalid

  This doesn't seem right
• Launch program

  Counts toward the pre-go-live project or release board.
• messaging

  Improvements or additions to messaging
• Needs: legal review

  Legal or compliance should look at content or claims before publishing.
• Needs: product or GTM

  Product, marketing, or GTM should confirm scope, naming, or positioning.
• P0 - launch blocker

  Must close or explicitly accept risk before / at go-live. (Same as backlog “P0”.)
• P1 - important soon

  Do right after launch if not blocking. (Same as backlog “P1”.)
• P2 - backlog

  When there is capacity. (Same as backlog “P2”.)
• product-update