Labels

• kind/data-scientist

  Connects an issue/PR with a particular user persona.
• kind/deprecation

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

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

  Indicates an issue/PR is related to human interaction and experience.
• kind/feature

  Categorizes issue or PR as related to a new feature.
• kind/general-public

  Connects an issue/PR with a particular user persona.
• kind/governance

  Indicates an issue/PR is related to governance.
• kind/handbook

  Indicates an issue/PR is related to a handbook.
• kind/marketing

  Indicates an issue/PR is related to marketing.
• kind/metrics

  Indicates an issue/PR is related to metrics.
• kind/news

  Indicates an issue/PR is related to project news and outreach.
• kind/onboarding

  Indicates an issue/PR is related to onboarding.
• kind/open-source-developer

  Connects an issue/PR with a particular user persona.
• kind/question

  Categorizes issue or PR as a support question.
• kind/sigs

  Indicates an issue/PR is related to Special Interest Groups (SIGs)
• kind/task

  Issues that clearly identify an actionable task, scoped appropriately.
• kind/undergrad-student

  Connects an issue/PR with a particular user persona.
• kind/user-story

  Categorizes an issue as capturing a user story
• kind/website

  Indicates an issue/PR is related to project web presence.
• lgtm

  Indicates that a PR is ready to be merged.
• lifecycle/active

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

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

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

  Denotes an issue or PR has remained open with no activity and has become stale.
• needs-ok-to-test

  Indicates a PR that requires an org member to verify it is safe to test.
• needs-rebase

  Indicates a PR cannot be merged because it has merge conflicts with HEAD.
• ok-to-test
• priority/awaiting-more-evidence

  Lowest priority. Possibly useful, but not yet enough support to actually get it done.
• priority/backlog

  Higher priority than priority/awaiting-more-evidence.
• priority/critical-urgent

  Highest priority. Must be actively worked on as someone's top priority right now.