Skip to content

No labels!

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

89 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
api-review
api-review
Categorizes an issue or PR as actively needing an API review.
approved
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
1
area/comment
area/comment
Issues or PRs related to the Halo Comment
area/console
area/console
Issues or PRs related to the Halo Console
41
area/core
area/core
Issues or PRs related to the Halo Core
98
area/docs
area/docs
Issues or PRs related to the Halo Documentation
area/editor
area/editor
Issues or PRs related to the Editor
24
area/plugin
area/plugin
Issues or PRs related to the Plugin Provider
25
area/theme
area/theme
Issues or PRs related to the Theme Provider
6
area/ui
area/ui
Issues or PRs related to the Halo UI
31
*as-designed
*as-designed
Described behavior is as designed
cherry-pick-approved
cherry-pick-approved
Indicates a cherry-pick PR into a release branch has been approved by the release branch manager.
confirmation-pending
confirmation-pending
1
confirmed
confirmed
Issue has been confirmed by VS Code Team member
dependencies
dependencies
Pull requests that update a dependency file
*dev-question
*dev-question
development questions
do-not-merge/blocked-paths
do-not-merge/blocked-paths
Indicates that a PR should not merge because it touches files in blocked paths.
do-not-merge/cherry-pick-not-approved
do-not-merge/cherry-pick-not-approved
Indicates that a PR is not yet approved to merge into a release branch.
do-not-merge/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
1
do-not-merge/invalid-commit-message
do-not-merge/invalid-commit-message
Indicates that a PR should not merge because it has an invalid commit message.
do-not-merge/invalid-owners-file
do-not-merge/invalid-owners-file
Indicates that a PR should not merge because it has an invalid OWNERS file in it.
do-not-merge/release-note-label-needed
do-not-merge/release-note-label-needed
Indicates that a PR should not merge because it's missing one of the release note labels.
2
do-not-merge/work-in-progress
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
1
*duplicate
*duplicate
Issue identified as a duplicate of another issue(s)
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
7
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
8
kind/api-change
kind/api-change
Categorizes issue or PR as related to adding, removing, or otherwise changing an API
1
kind/bug
kind/bug
Categorizes issue or PR as related to a bug.
15
kind/cleanup
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
1
kind/deprecation
kind/deprecation
Categorizes issue or PR as related to a feature/enhancement marked for deprecation.