Labels
Labels
20 labels
- Issues or pull requests that change public APIs (config, REST)
- A problem with current functionality, as opposed to missing functionality (enhancement)
- Issues caused by or requiring changes to the build system (scripts or Docker image)
- Pull requests that update a dependency file
- Issues related to the documentation
- New features or improvements of some kind, as opposed to a problem (bug)
- Issues closed and untouched for a long time, together with being locked for discussion
- Pull requests that update GitHub Actions code
- Pull requests that update Go code
- Good starting points for new contributors
- The maintainer takes responsibility for this PR being merged
- New issues needed to be validated
- Used only when we want to keep an issue open for visibility, but the real problem is somewhere else
- Legacy label used in the past for pull requests merged to the main tree
- Issues that require a change to the protocol (BEP, relay, discovery)
- Bugs that have never been in a released stable version, and as such excluded from the release notes
- The PR is considered a trivial change, for review purposes
- Issues related to the graphical user interface
- Issues that require more information from the author on how to reproduce