This docs contains information on how we use GitHub labels on issues and pull requests.
| Name | Issue | PR | Usage |
|---|---|---|---|
bug |
✅ | Indentifies reported bugs | |
cherry pick required |
✅ | Indentifies pull requests that need to be cherry picked | |
cherry pick completed |
✅ | Indentifies pull requests that were successfully cherry picked | |
dependencies |
✅ | Indentifies pull requests updating a dependency | |
documentation |
✅ | Indentifies issues related to documentation | |
documentation required |
✅ | Indentifies pull requests that need to be documented | |
documentation completed |
✅ | Indentifies pull requests that were successfully documented | |
duplicate |
✅ | ✅ | Identifies a duplicate issue or pull request |
enhancement |
✅ | Indentifies feature requests | |
github_actions |
✅ | Indentifies pull requests related to GitHub actions | |
go |
✅ | Indentifies pull requests related to golang packages |
|
good first issue |
✅ | Indentifies issues that are well suited for new contributors | |
help want |
✅ | Indentifies issues that need help from the community | |
release notes required |
✅ | Indentifies pull requests that need release notes | |
release notes completed |
✅ | Indentifies pull requests that have a corresponding release note | |
triage |
✅ | Indentifies issues that need to be triaged |