Labels

• A0-needs_burnin

  Pull request needs to be tested on a live validator node before merge. DevOps is notified via matrix
• A1-insubstantial

  Pull request requires no code review (e.g., a sub-repository hash update).
• A2-stale

  Pull request did not receive any updates in a long time. No review needed at this stage. Close it.
• A3-backport

  Pull request is already reviewed well in another branch.
• A4-backport-stable2506

  Pull request must be backported to the stable2506 release branch
• A4-backport-stable2509

  Pull request must be backported to the stable2509 release branch
• A4-backport-stable2512

  Pull request must be backported to the stable2512 release branch
• A4-backport-stable2603

  Pull request must be backported to the stable2603 release branch
• A4-backport-unstable2507

  Pull request must be backported to the unstable2507 release branch
• A4-backport-unstable2604

  Pull request must be backported to the unstable2604 release branch
• A5-run-CI

  Run CI on draft PR
• bug
• C1-mentor

  A task where a mentor is available. Please indicate in the issue who the mentor could be.
• C2-good-first-issue

  A task for a first time contributor to become familiar with the Polkadot-SDK.
• C3-og-rust-bounty

  A task rewarded by the OG Rust bounty for successful completion. See https://ogrust.com/
• D0-easy

  Can be fixed primarily by duplicating and adapting code by an intermediate coder.
• D1-medium

  Can be fixed by a coder with good Rust knowledge but little knowledge of the codebase.
• D2-substantial

  Can be fixed by an experienced coder with a working knowledge of the codebase.
• D3-involved

  Can be fixed by an expert coder with good knowledge of the codebase.
• dependencies

  Pull requests that update a dependency file
• feature
• GHA-coverage

  run coverage workflow for this pr
• GHA-migration

  Temporary label for migrating CI to GHA
• I0-panic

  The node panics and exits without proper error handling.
• I1-security

  The node fails to follow expected, security-sensitive, behaviour.
• I10-unconfirmed

  Issue might be valid, but it's not yet known.
• I2-bug

  The node fails to follow expected behavior.
• I3-annoyance

  The node behaves within expectations, however this “expected behaviour” itself is at issue.
• I4-refactor

  Code needs refactoring.
• I5-enhancement

  An additional feature request.