Labels

• approved

  Pull requests that have been approved
• breaking-change

  Pull requests that would cause existing functionality to not work as expected
• bug-fix

  Pull requests that fix a bug
• changes-requested

  Pull requests with requested changes
• chore

  Pull requests that does something "boring", yet important, e.g. cleaning up code
• dependencies

  Pull requests that update a dependency file
• discussion

  Pull requests that needs discussions, e.g. regarding controversial/big changes
• do-not-merge/hold

  Pull request is on hold (e.g. waiting for something else to be merged), and should not be merged
• do-not-merge/WIP

  Pull requests that are "work in progress", and should not be merged
• docs

  Pull requests that update or add documentation
• duplicate
• enhancement

  Pull requests that make enhancements, instead of just purely new features
• flawless

  Pull requests with "flawless" code, e.g. formatting or simple renaming. Should be used with caution!
• future-is-now

  Pull requests that utilize cutting-edge technology or just a cool new feature
• future-was-2-years-ago

  Pull requests that introduce technologies which should have been "long" ago
• help-wanted

  Pull requests that want help in the form of contributions
• invalid
• javascript

  Pull requests that update javascript code
• lego-bricks

  Pull requests related to lego-bricks
• need-before-2050

  Pull requests that have been in progress for far too long
• new-feature

  Pull requests that introduce a new feature
• priority:high

  Pull requests that have high priority, and should therefore be prioritized
• question

  Pull requests with an unresolved question
• ready-to-merge

  Pull requests that have been approved and are ready to be merged
• review-needed

  Pull requests that need review
• security

  Pull requests that address a security vulnerability
• small-fix

  Pull requests that fix something small
• technical-debt

  Pull requests that reduces technical debt
• testing-needed

  Pull requests that need testing, e.g. stress tests by users or specs
• tests

  Pull requests that add or update tests