Labels

• A-ci

  Related to CI/CD
• A-cleanup

  Related to improving quality of the codebase
• A-meta

  Related to changes in the contributor workflow and planning
• C-bug

  An unexpected or incorrect behaviour
• C-debt

  A section of code is hard to understand or change
• C-discussion

  A discussion about direction and design
• C-documentation

  An addition or correction to our docs
• C-enhancement

  Improvement to an existing feature
• C-feature

  Related to a new feature
• C-perf

  A performance-improving change
• C-question

  Further information is requested
• C-regression

  A bug that was previously fixed
• C-security

  Relevant to improving security
• C-spike

  A bit of research that will likely produce more work or informs future work
• C-test

  A change that impacts how or what we test
• C-tracking-issue

  An issue that collects information about a broad development initiative
• D-complex

  Quite challenging from either a design or technical perspective
• D-good-first-issue

  Nice and easy! A great choice to get started
• M-changelog

  This change should be included in the changelog
• M-prevent-stale

  Prevents old inactive issues/PRs from being closed due to inactivity
• P-critical

  This must be fixed immediately or contributors and users will be severely impacted
• P-high

  This is particularly urgent, and deserves immediate attention
• S-blocked

  This cannot more forward until something else changes
• S-breaking

  This PR includes a breaking change
• S-controversial

  This requires good review before it can be merged
• S-duplicate

  This issue or PR already exsts
• S-feedback-wanted

  This issue or PR is looking for feedabck
• S-needs-benchmark

  This set of changes needs performance benchmarking to double-check that they help
• S-needs-design

  This issue requires design work
• S-needs-investigation

  This issue requires investigation