Repository navigation
Contributing to Radarr #48
Pinned
Starosdev
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Contributing
Thank you for your interest in contributing to Radarr! This is an actively maintained fork of the original Radarr/Radarr project.
Before You Start
Branch Workflow
We use a Gitflow-style workflow:
master- Production-ready code (protected)develop- Integration branch for featuresfeature/*- New featuresfix/*- Bug fixeshotfix/*- Urgent production fixesCreating a PR
developdevelop(nevermaster, unless it is a hotfix)Code Style
varpreferred,_camelCasefor private fieldsRun linting before submitting frontend changes:
yarn lint --fix yarn stylelint-linux # macOS/LinuxProject Structure
Radarr is a monorepo containing:
The codebase uses the legacy
NzbDronenamespace from its predecessor project. Project directories useNzbDrone.*but.csprojfiles are namedRadarr.*.Development Setup
Tools Required
global.jsonfor exact version)corepack enable)Getting Started
Building the Frontend
Building the Backend
Visual Studio / Rider
src/Radarr.slnRadarr.Console, framework tonet8.0Command Line
Running Tests
Radarr uses NUnit for its test suite. Test assemblies are output to
_tests/.We encourage writing unit tests for any backend code changes. We currently require 80% coverage on new code when submitting a PR.
Contributing Code
develop, do not mergeNew:orFixed:prefixes for non-maintenance changesTranslation
Radarr uses a self-hosted Weblate instance for translations. Translation files are stored at
src/NzbDrone.Core/Localization.The English translation (
en.json) is the source for all other translations and is managed in the GitHub repo.Adding Translation Strings
Backend
Frontend
All reactions