Cutlery/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2025-08-11 09:13:54 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updated Contributing to Jellyfin (markdown)

Joshua M. Boniface 2019-01-01 16:20:40 -05:00
parent 4ea42889a5
commit cb8b39e40f
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Contributing-to-Jellyfin.md

@ -56,7 +56,7 @@ If it's your first time contributing code, please add yourself to the `CONTRIBUT
When submitting a new PR, please ensure you do the following things. If you haven't, please read [How to Write a Git Commit Message](https://chris.beams.io/posts/git-commit/) as it is a great resource for writing useful commit messages.
* Write a good title that quickly describes what has been changed. For example, "Adds LDAP support to Jellyfin".
* For anything but the most trivial changes that can be described fully in the title, write a detailed PR body to describe, in detail:
* For anything but the most trivial changes that can be described fully in the title, write a PR body to describe, in as much detail as possible:
1. *Why* the changes are being made. Reference specific issues with keywords (`fixes`, `closes`, `addresses`, etc.) if at all possible.
1. *How*, in broad strokes, you approached the issue (if applicable) and briefly describe the changes, especially for large PRs.
* Manually update the target branch from `master` to `dev`; PRs against `master` are only considered in the most exceptional circumstances and all new work should go to `dev`. GitHub does not know this, so you must be explicit with every PR.