Skip to content
This repository has been archived by the owner on Oct 30, 2023. It is now read-only.

No labels!

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

87 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
kind/data-engineer
kind/data-engineer
Connects an issue/PR with a particular user persona.
kind/data-scientist
kind/data-scientist
Connects an issue/PR with a particular user persona.
kind/deprecation
kind/deprecation
Categorizes issue or PR as related to a feature/enhancement marked for deprecation.
kind/documentation
kind/documentation
Categorizes issue or PR as related to documentation.
kind/experience
kind/experience
Indicates an issue/PR is related to human interaction and experience.
kind/feature
kind/feature
Categorizes issue or PR as related to a new feature.
kind/general-public
kind/general-public
Connects an issue/PR with a particular user persona.
kind/governance
kind/governance
Indicates an issue/PR is related to governance.
kind/handbook
kind/handbook
Indicates an issue/PR is related to a handbook.
kind/marketing
kind/marketing
Indicates an issue/PR is related to marketing.
kind/metrics
kind/metrics
Indicates an issue/PR is related to metrics.
kind/news
kind/news
Indicates an issue/PR is related to project news and outreach.
kind/onboarding
kind/onboarding
Indicates an issue/PR is related to onboarding.
kind/open-source-developer
kind/open-source-developer
Connects an issue/PR with a particular user persona.
kind/question
kind/question
Categorizes issue or PR as a support question.
kind/sigs
kind/sigs
Indicates an issue/PR is related to Special Interest Groups (SIGs)
kind/task
kind/task
Issues that clearly identify an actionable task, scoped appropriately.
kind/undergrad-student
kind/undergrad-student
Connects an issue/PR with a particular user persona.
kind/user-story
kind/user-story
Categorizes an issue as capturing a user story
kind/website
kind/website
Indicates an issue/PR is related to project web presence.
lgtm
lgtm
Indicates that a PR is ready to be merged.
lifecycle/active
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
lifecycle/frozen
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
lifecycle/rotten
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
lifecycle/stale
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
needs-ok-to-test
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
needs-rebase
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
priority/awaiting-more-evidence
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
priority/backlog
priority/backlog
Higher priority than priority/awaiting-more-evidence.
priority/critical-urgent
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.