This repository uses labels to help contributors and maintainers categorize issues and pull requests consistently.
high priority— Critical work that must be addressed before the next release.medium priority— Important work that should be handled soon, but is not urgent.low priority— Nice-to-have improvements or background tasks.
good first issue— A beginner-friendly issue with a clear scope and minimal setup.wave-ready— A contribution that is eligible for Drips Wave funding and has a well-defined implementation plan.
bug— A defect in the contract, tests, docs, or tooling.testing— Issues related to test coverage, missing tests, or test infrastructure.documentation— Changes to docs, guides, README content, or contributor-facing materials.security— Security reviews, audits, vulnerability fixes, or hardening work.
needs review— Ready for maintainer review.needs more info— Requires clarification from the issue author before work can begin.in progress— Work is currently underway and not yet ready for review.
- Apply one priority label for triage.
- Use one or more type labels to describe the work area.
- Add
good first issueonly for issues that are easy to onboard new contributors. - Add
wave-readywhen the issue is fully scoped, testable, and eligible for Drips Wave support.
This taxonomy is intended to improve consistency across issues and pull requests. If a label is missing or needs refinement, open an issue to suggest additions or updates.