Labels

• accepted

  Issues with this label are issues that the core team has accepted on to the roadmap.
• accessibility

  An issue concerning accessibility.
• beginner

  Good for newcomers to the project.
• blocked

  The issue cannot be resolved until some other issue has been closed.
• bug

  An issue describing unexpected or malicious behaviour.
• ci

  Anything related to continuous integration
• confirmed

  This label indicates that the issue has been reproduced and verified by the core team.
• dependencies

  Pull requests that update a dependency file
• design

  Issues related to the visual design of liquid.
• discussion

  Discussions should not happen in issues. If they do... well, we have a label for that.
• documentation

  Improvements or additions to documentation
• duplicate

  This issue or pull request already exists.
• dx

  Anything related to developer experience
• feature

  Issues that describe new features.
• github_actions

  Pull requests that update GitHub Actions code
• has workaround

  A workaround exists to handle the issue until it is fixed.
• help wanted

  Core maintainers are asking for help from the community.
• improvement

  Not a bug nor a feature. Refactoring of code would likely have this label.
• in progress

  This label indicates that the issue is currently being worked on.
• javascript

  Pull requests that update Javascript code
• linting

  Anything related to linting.
• needed: design decision

  Issues that need a design decision are blocked for development.
• needed: documentation

  If something is lacking documentation, this label will be assigned.
• needed: more information

  This label indicates that a reply with more information is required from the issue reporter.
• needed: replication

  This label indicates that a bug has been reported, but has not been successfully replicated yet.
• needed: tests

  This label indicates that a better test coverage is required to resolve the issue.
• needed: votes

  Enhancement suggestion which needs votes, before it gets addressed by the contributors.
• priority: high

  Issues with this label should be resolved as quickly as possible.
• priority: low

  Issues with this label won’t have the immediate focus of the core team.
• question

  Not really an issue but more a question.