Labels

• airtable-ignore

  Issues with this label will be ignored by Airtable's sync job
• breaking

  Issues that introduce logic with breaking changes/backwards incompatibility
• duplicate

  Issues that already exist elsewhere
• effort: 1
• effort: 13
• effort: 2
• effort: 3
• effort: 5
• effort: 8
• good first issue

  Issues that are suitable for newcomers to the codebase
• help

  Help and/or attention is needed to progress these issues
• priority: 2day

  Issues that need are not critical, but still need to be looked at
• priority: now

  Issues that need to be actioned immediately, before all other issues
• priority: soon

  Issues that we should look to work on shortly
• state: approved

  Issues that are approved and ready to be proceeded with
• state: blocked

  Issues that are blocked (prevented from progressing) by another issue(s)
• state: inactive

  Issues that are invalid, abandoned, or not suitable/outside scope
• state: pending

  Issues that are active, but need a few things to happen before resolution
• type: bug

  Issues that target unintentional behavior
• type: chore

  Issues for mundane tasks, typically not involving programming
• type: docs

  Issues related to documentation and information
• type: enhancement

  Issues that adapt/iterate on existing features
• type: feature

  Issues for brand new functionality, features, mechanics, etc.
• type: renovate
• type: security

  Issues that target vulnerabilities
• type: testing

  Issues that introduce/modify tests and/or benchmarks
• work: chaotic

  Issues that are chaotic, novel practices used
• work: clear

  Issues that are clear (obvious), best practices used
• work: complex

  Issues that are complex, emergent practices used
• work: complicated

  Issues that are complicated, good practices used