Agentic Labeler

Labeling rules for the dotnet/maui repository. These rules are the canonical source of truth for how issues and PRs should be labeled. They are consumed by the agentic-labeler gh-aw workflow and can also be used standalone for batch evaluation or interactive labeling.

Label discovery

• Fetch the current list of labels using the list_label MCP tool (provided by the labels toolset). Note the singular name — it is list_label, not list_labels.
• Important pagination caveat: the list_label tool only returns the first ~100 labels (no pagination). This repo has ~440 labels, so many area-*, platform/*, and status labels will be missing from the listing. If you have a strong candidate label name in mind that isn't in the listing, verify it exists with the get_label tool before adding it. The label families enumerated below (area-*, platform/*, t/*, s/*, i/*, p/*) are reliable guides; use get_label for anything else.
• You may apply any existing label, not just area-* and platform/*. Examples of other useful label families that exist in this repo (with exact names — emoji suffixes are part of the label and must be matched verbatim):
  • Kind: t/bug, t/enhancement ☀️, t/docs 📝, t/breaking 💥, t/native-embedding, t/desktop, t/a11y
  • Status / signal (issues): i/regression, s/needs-repro, s/needs-info, s/needs-attention, s/duplicate 2️⃣, s/no-repro, s/not-a-bug
  • Priority: p/0, p/1, p/2, p/3
• PR-specific status caveat: do not apply s/needs-info or s/needs-repro to pull requests — repo automation rewrites or removes them and posts a comment. On PRs, use s/pr-needs-author-input instead when more information is needed.
• Do not create new labels. Only labels that already exist in the repository will be accepted.

Labeling rules

area-* labels (issues and PRs)