Labels

• area-test
• autosubmit
• bad-test

  Report tests in need of updates. When closed, the tests should be considered good
• cla: no
• cla: yes
• closed-as-intended

  Closed as the reported issue is expected behavior
• closed-cannot-reproduce

  Closed as we were unable to reproduce the reported issue
• closed-duplicate

  Closed in favor of an existing report
• closed-invalid

  Closed as we don't believe the reported issue is generally actionable
• closed-not-planned

  Closed as we don't intend to take action on the reported issue
• closed-obsolete

  Closed as the reported issue is no longer relevant
• closed-stale

  Closed as the issue or PR is assumed stale.
• contributions-welcome

  Contributions welcome to help resolve this (the resolution is expected to be clear from the issue)
• dependencies

  Pull requests that update a dependency file
• good first issue

  A good starting issue for contributors (issues with this label will appear in /contribute)
• needs-info

  Additional information needed from the issue author
• P0

  A serious issue requiring immediate resolution
• P1

  A high priority bug; for example, a single project is unusable or has many test failures
• P2

  A bug or feature request we're likely to work on
• P3

  A lower priority bug or feature request
• status-blocked

  Blocked from making progress by another (referenced) issue
• type-bug

  Incorrect behavior (everything from a crash to more subtle misbehavior)
• type-code-health

  Internal changes to our tools and workflows to make them cleaner, simpler, or more maintainable
• type-documentation

  A request to add or improve documentation
• type-enhancement

  A request for a change that isn't a bug
• type-infra

  A repository infrastructure change or enhancement
• type-question

  A question about expected behavior or functionality
• type-ux

  A user experience or user interface related issue