Unlabeled
affected-few
affected-very-few
approved to merge
area-aspnet
area-blazor
area-compiler
Umbrella for all compiler issues
area-infrastructure
area-localization
area-parsing
author: migration bot 🤖
The issue was created by a issue mover bot. The author may not be the actual author
auto-merge
Squash merge once all PR checks are complete and reviewers have approved
blocked
Blocked on a partner team
bug
Something isn't working
code-quality
community
Community PR
concept-language.design
enhancement
Small improvement request
external
Scope involves an area outside of the repo
feature parity
Feature exists in the pre-LSP editor
feature request
Large improvement request
feature-colorization
feature-completion
feature-formatting
flaky test
good first issue
Good for newcomers
✔️ resolution: answered
Question has been answered
✔️ resolution: by design
✔️ resolution: duplicate
This issue or pull request already exists
✔️ resolution: fixed
✔️ resolution: won't fix
A real bug, but triage feels that the issue is not impactful enough to spend time on
help wanted
Good issue for community contributions
infra-support
infra-support
investigate
javascript
Pull requests that update Javascript code
Merge Conflicts
needs approval
needs design review
needs more info
.NET
Pull requests that update .net code
New Feature: Fuse
* NO MERGE *
Do not merge this PR as long as this label is present
no recent activity
on-deck
To be reviewed if it should be in next sprint
perf 📊
Priority:0
Priority:1
Priority:2
Priority:3
question
Further information is requested
Razor
reliability 📊
servicing-approved
.NET Tactics Approval Granted
servicing-consider
.NET Tactics Approve Request
severity-blocking
severity-major
severity-nice-to-have
task
tech-debt
test scenario
tooling big rock ⚪
tooling-compiler-repo-merge
Temp label to track tooling and compiler repo merge work
triaged
type-dependency update 🔼
type-merge forward ⏩
untriaged
user story
vs
vs-insertion
vscode
vsmac
No labels found. Sorry about that.