Updated Issue Guidelines (markdown)

Joshua M. Boniface 2019-01-03 15:14:15 -05:00
parent 86eb8de7df
commit 1119180dc8

@ -50,12 +50,19 @@ These labels help determine how critical an issue is:
* `enhancement`: An issue that requests a modification of an existing feature. * `enhancement`: An issue that requests a modification of an existing feature.
* `feature`: An issue that requests a new feature not present in Jellyfin. * `feature`: An issue that requests a new feature not present in Jellyfin.
### Management Lables ### Management Labels
Finally there are a few more labels to assist in managing the project: These labels help assist in managing the project and direction:
* `Good first issue`: Something that should be very straightforward to do, and is a great place to get started. * `Good first issue`: Something that should be very straightforward to do, and is a great place to get started.
* `help wanted`: An issue that currently has no clear expert within the project and could use outside assistance. * `help wanted`: An issue that currently has no clear expert within the project and could use outside assistance.
* `roadmap`: A meta-issue related to the future roadmap of the project. * `roadmap`: A meta-issue related to the future roadmap of the project.
* `documentation`: An issue related to the documentation of the project. * `documentation`: An issue related to the documentation of the project.
* `fork`: An issue related to the forking from Emby. * `fork`: An issue related to the forking from Emby.
### PR Labels
These labels apply only to Pull Requests for administrative purposes:
* `WIP`: A Work-in-progress PR that is not yet ready to be merged, usually blocked by further work from the contributor or a testing requirement.
* `requires testing`: A PR that has not been tested in a live environment yet. Any major backend-affecting PRs should be tested before being merged to avoid regressions.