Labels

• A-blocked

  issue or PR is blocked until something else changes.
• A-debug

  issue requires detective debug work to figure out what's going wrong.
• A-design

  issue requires design work to think about how it would best be accomplished.
• A-in-QA-or-regression

  pull request or issues is currently in QA or regression testing phase.
• A-stale

  issue or PR is deprecated and needs to be closed.
• A-tooBig

  issue or PR needs to be broken down to smaller parts.
• A-triage

  issue description needs refactor and/or labeled.
• C-chaotic

  Unpredictable nature of this task/changes makes its chaotic.
• C-complex

  Complex changes across multiple modules. Possibly will require additional research.
• C-simple

  Minor changes changes, no additional research needed. Good first issue/review.
• dependencies

  Pull requests that update a dependency file
• Epic

  Issue used to track development status of a complex feature, aggregates several issues
• Feature-branch

  pull request from feature branch to origin.
• go

  Pull requests that update go code
• good first issue

  issues that are suitable for first-time contributors.
• javascript

  Pull requests that update Javascript code
• P-critical

  this must be fixed immediately or contributors or users will be severely impacted.
• P-high

  this should be addressed ASAP.
• P-low

  this is mostly nice to have.
• Release

  pull request with next release changes.
• S-babe

  issues related to block production functionality.
• S-ci

  issue related to continuous integration tasks or piplelines.
• S-cli

  issue related to Gossamer CLI.
• S-crypto

  issues related to the lib/crypto package.
• S-dependencies

  issues related to polkadot host disputes subsystem functionality.
• S-doc

  documentation related.
• S-grandpa

  issues related to block finality.
• S-infrastructure

  issues related to infrastructure and DevOps.
• S-network

  issues related to the dot/network package.
• S-rpc

  issues related to the dot/rpc package.