Skip to content

No labels!

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

aq-pr-triaged
aq-pr-triaged
Tracking label for the PR review team.
area-controls
area-controls
Control-related feedback.
assigned-to-author
assigned-to-author
Issue assigned to topic owner.
broken-link
broken-link
404
Change sent to author
Change sent to author
Topic owner notified of update to issue.
code-of-conduct
code-of-conduct
Spam, rant, or violates Microsoft's code of conduct.
do-not-merge
do-not-merge
PR is being processed and awaiting review/approval.
doc-bug
doc-bug
Topic has missing, outdated, unclear, confusing info, or has broken functionality.
doc-enhancement
doc-enhancement
Topic could benefit from additions/improvements, but customer is not blocked.
doc-idea
doc-idea
Request to contribute, or collaborate on, a new topic.
doc-provided
doc-provided
Topic exists that addresses issue but customer could not find.
docs-editor-pilot
docs-editor-pilot
docs-experience
docs-experience
Not topic feedback. General Docs platform feedback.
duplicate
duplicate
Duplicates other feedback.
eng-triaged
eng-triaged
Issue has been triaged by engineering team responsible.
forum
forum
Not topic feedback. Direct customer to Microsoft product/support forum or StackOverflow.
high-viewership
high-viewership
Topic has high page views.
in-progress
in-progress
PR is being processed.
kudos
kudos
Positive feedback, praise, thanks, etc.
loc
loc
Topic has a localization/globalization issue.
needs-more-info
needs-more-info
Customer to provide more information. Issue assigned to the customer who filed the issue.
Pri1
Pri1
Topic is in the top 25% of page views for the repo or was first published in the preceding 45 days.
Pri2
Pri2
Topic is in the second 25% of page views for the repo.
Pri3
Pri3
Topic is in the bottom 50% of page views for the repo or was not created via Feedback control.
product-feedback
product-feedback
Not topic feedback. Direct customer to product feedback process.
product-question
product-question
Not topic feedback. Direct customer to product feedback process.
PRRT not required
PRRT not required
PR does not require review by the editors.
PRRT required
PRRT required
PR requires review by the editors against the PR checklist.
ready-to-merge
ready-to-merge
PR is ready to merge into specified branch.
resolved-by-customer
resolved-by-customer