4.8 KiB
Contributing Guidelines
👍🎉 First off, thanks for taking the time to contribute! 🎉👍
Here you will find a set of guidelines for contributing to TRaSH Guides, Which you can find HERE, These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
Guidelines
- Make sure you're editing the latest version.
- If you propose changes make sure it doesn't break anything else in the Guides.
- Make sure that after the changes you don't get any markdownlint errors
- If the
metadata.json
andmetadata.schema.json
needs changes, announce it first in the Discord#development
channel and pingvoidpointer
andnitsua
so the 3rd party apps don't break ‼️
Branch naming
We're trying to be as consistent as possible for automation of the changelog.
- feat/xxx Commits, that adds a new feature
- fix/xxx Commits, that fixes a bug/issue
- style/xxx Commits, that do not affect the meaning (white-space, formatting, missing semi-colons, etc)
- chore/xxx Miscellaneous commits (administrative / cleanup / backend)
Where 'xxx' can stand for Starr/Sonarr/Radarr/Guide etc
Examples:
feat/Starr-ELEANOR-to-Scene-CF
feat/Radarr-CiNEPHiLES-to-Remux-Tier-02
feat/maintenance
fix/dv-hdr10-cf-should-match-dv-hdr10+
Source{:target="_blank" rel="noopener noreferrer"}
Pull Request naming
We're trying to be as consistent as possible for automation of the changelog.
- feat(xxx): Commits, that adds a new feature
- fix(xxx): Commits, that fixes a bug/issue
- style(xxx): Commits, that do not affect the meaning (white-space, formatting, missing semi-colons, etc)
- chore(xxx): Miscellaneous commits (administrative / cleanup / backend)
Where 'xxx' can stand for Starr/Sonarr/Radarr/Guide etc
Examples:
feat(starr): add ELEANOR to Scene CF
feat(radarr): add CiNEPHiLES to Remux Tier 02
feat(maintenance): various changes to the Starr CFs
fix(starr): DV HDR10 CF should match DV HDR10+
Source{:target="_blank" rel="noopener noreferrer"}
When doing a PR that is WIP
When doing a PR that is in-progress and not yet complete / ready for review not yet done fully please ensure it is a DRAFT Pull Request
Radarr/Sonarr Custom Format (JSON)
- Custom Format name needs to match json name ‼️
- No hashcode can exists multiple times ‼️
- JSON file names are always written in small letters, spaces are replaced by a dash, no spaces or special characters except a dash ‼️
- When adding the hashcode for Radarr use the following naming
CF_name
on the following link+example{:target="_blank" rel="noopener noreferrer"}. - When adding the hashcode for Radarr Anime use the following naming
Radarr Anime CF_name
on the following link+example{:target="_blank" rel="noopener noreferrer"}. - When adding the hashcode for Sonarr use the following naming
Sonarr CF_name
on the following link+example{:target="_blank" rel="noopener noreferrer"}. - When adding the hashcode for Sonarr Anime use the following naming
Sonarr Anime CF_name
on the following link+example{:target="_blank" rel="noopener noreferrer"}. - Provide a link to your regex example of your Custom Format using the following Template{:target="_blank" rel="noopener noreferrer"}.
- When adding a RlsGRp to a Custom Format for what ever reason, please add in the PR why it's added/removed/moved.
When adding a regex test case
- Replace the actual movie name with
Movie
. - Replace the actual series name with
Series
. - Remove the actual Series title.
- Replace the actual group name with
RlsGrp
When updating or adding a new CF the test case url needs to be added to the json.
{
"trash_id": "hashcode",
"trash_score": "score",
"trash_regex": "https://regex101.com/r/pADWJD/5",
"name": "CF_name",
YAML file naming
- If a hashcode is needed No hashcode can exist multiple times ‼️
- YAML file names are always written in small letters, spaces are replaced by a dash, no spaces or special characters except a dash ‼️
Recommendations
- use VSCode{:target="_blank" rel="noopener noreferrer"} for editing with the following extension markdownlint{:target="_blank" rel="noopener noreferrer"}