awesome-jellyfin/CONTRIBUTING.md

Contribution Guidelines

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Pull Requests

Ensure your pull request adheres to the following guidelines:

• Use the Conventional Commits specification (<type>[optional scope]: <description>)
• Alphabetical Sorting: Items in README.md must be sorted alphabetically. See Sorting Rules.
• Generated Content: Some files, like CLIENTS.md are automatically generated from files. You should only edit the original source files from which they're generated from. See Generated Content.
• Search previous suggestions before making a new one, as yours may be a duplicate
• New categories, or improvements to the existing categorization are welcome
• Keep descriptions short and simple, but descriptive and non-promotional

Thank you for your suggestions!

Sorting Rules

Certain lists within this repository should be kept alphabetically sorted, according to a canonical version of each item. The rules for deriving this canonical version (used for sorting) are as follows:

1. Square Brackets:
   • If the line contains text in square brackets (e.g., - [My Item]), only that bracketed text is used to determine the item's position.
   • If there are no square brackets, the entire line (minus the leading "- " if present) is used.
2. Removing Characters:
   • From that resulting text, remove the following characters for sorting:

     [ -_().`',:!?]
     

If two items end up with the same canonical text, their original order is preserved.

Note

A bot will automatically check your PR for correct order.

• You can manually fix sorting or ask a maintainer to run /sort-check -fix (if needed).

Generated Content

Some files in this repository are automatically generated from other source files. For example, CLIENTS.md is generated from assets/clients/clients.yaml.

• Do not edit these generated files directly. Instead, edit the original source files from which they’re generated.
• Each generated file clearly indicates that it is automatically generated.
• Once you push your changes to the source file, the project’s checks will automatically regenerate the corresponding output file.

Note

For pull requests, a preview of the updated generated files will appear in the Checks tab of the pull request.

Updating your PR

A lot of times, making a PR adhere to the standards above can be difficult. If the maintainers notice anything that we'd like changed, we'll ask you to edit your PR before we merge it. There's no need to open a new PR, just edit the existing one. If you're not sure how to do that, here is a guide on the different ways you can update your PR so that we can merge it.