Skip to content

normalize issue labels with other dart-lang repos #59282

@devoncarew

Description

@devoncarew

Hi - we're working to normalize issue labels across the dart-lang repos. This is particularly topical for this repo, as I imagine the issues here will be transferred into the dart-lang/sdk repo. Here's the current diff of this repo's labels vs the canonical dart-lang set (hosted at dart-lang/.github):

  (rename) [ux]: rename => type-ux, color => #fff9e3, description => "A user experience or user interface r..."
  (update) [autosubmit]: color => #1D76DB
  (update) [contributions-welcome]: color => #C2E0C6, description => "Contributions welcome to help resolve..."
  (update) [good first issue]: color => #C2E0C6, description => "A good starting issue for contributor..."
  (update) [needs-info]: color => #444444, description => "Additional information needed from th..."
  (update) [P0]: description => "A serious issue requiring immediate r..."
  (update) [P1]: color => #f9c0b4, description => "A high priority bug; for example, a s..."
  (update) [P2]: description => "A bug or feature request we're likely..."
  (update) [P3]: color => #FEF2C0, description => "A lower priority bug or feature request"
  (update) [type-bug]: color => #fff9e3, description => "Incorrect behavior (everything from a..."
  (update) [type-code-health]: color => #fff9e3, description => "Internal changes to our tools and wor..."
  (update) [type-documentation]: color => #fff9e3, description => "A request to add or improve documenta..."
  (update) [type-enhancement]: color => #fff9e3, description => "A request for a change that isn't a bug"
  (update) [type-question]: color => #fff9e3, description => "A question about expected behavior or..."
  (add) [closed-as-intended]: #686868 "Closed as the reported issue is expected behavior"
  (add) [closed-cannot-reproduce]: #686868 "Closed as we were unable to reproduce the reported issue"
  (add) [closed-duplicate]: #686868 "Closed in favor of an existing report"
  (add) [closed-invalid]: #686868 "Closed as we don't believe the reported issue is generally actionable"
  (add) [closed-not-planned]: #686868 "Closed as we don't intend to take action on the reported issue"
  (add) [closed-obsolete]: #686868 "Closed as the reported issue is no longer relevant"
  (add) [closed-stale]: #686868 "Closed as the issue or PR is assumed stale."
  (add) [status-blocked]: #444444 "Blocked from making progress by another (referenced) issue"
  (add) [type-infra]: #fff9e3 "A repository infrastructure change or enhancement"
  (consistency) [dependency: analyzer]: avoid spaces; use lowercase-dashes to join words
  (consistency) [effective dart]: avoid spaces; use lowercase-dashes to join words
  (consistency) [false negative]: avoid spaces; use lowercase-dashes to join words
  (consistency) [false positive]: avoid spaces; use lowercase-dashes to join words
  (consistency) [lint proposal]: avoid spaces; use lowercase-dashes to join words
  (consistency) [lint request]: avoid spaces; use lowercase-dashes to join words
  (consistency) [needs internal testing]: avoid spaces; use lowercase-dashes to join words
  (consistency) [new language feature]: avoid spaces; use lowercase-dashes to join words
  (consistency) [NNBD]: avoid upper case; use lowercase names
  (consistency) [process]: avoid single word labels (prefer using a category prefix)
  (consistency) [pub]: avoid single word labels (prefer using a category prefix)
  (consistency) [set-flutter (dev)]: avoid spaces; use lowercase-dashes to join words
  (consistency) [set-internal (available)]: avoid spaces; use lowercase-dashes to join words
  (consistency) [status: accepted]: avoid spaces; use lowercase-dashes to join words
  (consistency) [status: closed]: avoid spaces; use lowercase-dashes to join words
  (consistency) [status: in progress]: avoid spaces; use lowercase-dashes to join words
  (consistency) [status: pending]: avoid spaces; use lowercase-dashes to join words
  (consistency) [style]: avoid single word labels (prefer using a category prefix)

Given the number of issues in this repo I think we should prep the repo with a bunch of manual label renames / adds / updates before we run the label normalization tool here; cc @pq.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2A bug or feature request we're likely to work ondevexp-linterIssues with the analyzer's support for the linter packagelegacy-area-analyzerUse area-devexp instead.type-taskA well-defined stand-alone task

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions