Private GIT

Skip to content
Snippets Groups Projects
Select Git revision
  • 9fdf9e869ff03af56f7c67eae348421f7d43acd8
  • master default protected
  • fix_nzb_cat
  • develop
  • guessit2-minimal
  • ssl_warning
  • UHD-qualities
  • fix_providers8
  • !
  • tvvault
  • provider_alpharatio
  • v5.1.1
  • v5.1
  • v5.0.3
  • v5.0.2
  • v5.0.1
  • v5.0
  • v4.2.1.07
  • v4.2.1.06
  • v4.2.1.05
  • v4.2.1.04
  • v4.2.1.03
  • v4.2.1.02
  • v4.2.1.01
  • v4.2.1.0
  • v4.2.0.6
  • v4.2.0.5
  • v4.2.0.4
  • v4.2.0.3
  • v4.2.0.2
  • v4.2.0.1
31 results

contributing.md

Blame
  • After you've reviewed these contribution guidelines, you'll be all set to contribute to this project.
    contributing.md 6.88 KiB

    Questions about SickRage?

    To get your questions answered, please ask on the #sickrage-issues IRC channel on irc.freenode.net

    Contributing to SickRage

    1. Getting Involved
    2. How To Report Bugs
    3. Tips For Submitting Code

    Getting Involved

    There are a number of ways to get involved with the development of SickRage. Even if you've never contributed code to an Open Source project before, we're always looking for help identifying bugs, cleaning up code, writing documentation and testing.

    The goal of this guide is to provide the best way to contribute to the official SickRage repository. Please read through the full guide detailing How to Report Bugs.

    Discussion

    If you think you've found a bug please file it in the bug tracker.

    Most of the SickRage development team can be found in the #sickrage-issues IRC channel on irc.freenode.net.

    How to Report Bugs

    Make sure it is a SickRage bug

    Many bugs reported are actually issues with the user mis-understanding of how something works (there are a bit of moving parts to an ideal setup) and most of the time can be fixed by just changing some settings to fit the users needs.

    If you are new to SickRage, it is usually a much better idea to ask for help first in the SickRage IRC channel. You will get much quicker support, and you will help avoid tying up the SickRage team with invalid bug reports.

    Try the latest version of SickRage

    Bugs in old versions of SickRage may have already been fixed. In order to avoid reporting known issues, make sure you are always testing against the latest build/source. Also, we put new code in the develop branch first before pushing down to the master branch (which is what the binary builds are built off of).

    Tips For Submitting Code

    Code

    NEVER write your patches to the master branch - it gets messy (I say this from experience!)

    ALWAYS USE A "TOPIC" BRANCH! Personally I like the branch-feature_name format that way its easy to identify the branch and feature at a glance. Also please make note of any issue number in the pull commit so we know what you are solving (it helps with cleaning up the related items later).

    Please follow these guidelines before reporting a bug:

    1. Update to the latest version — Check if you can reproduce the issue with the latest version from the develop branch.

    2. Use the search on sickrage-issues — check if the issue has already been reported. If it has been, please comment on the existing issue.

    3. Provide a means to reproduce the problem — Please provide as much details as possible, e.g. SickRage log files (obfuscate apikey/passwords), browser and operating system versions, how you started SickRage, and of course the steps to reproduce the problem.

    Feature requests

    Please follow the bug guidelines above for feature requests, i.e. update to the latest version and search for existing requests on FeatHub before posting a new request.. Feature Requests

    Pull requests

    Pull requests are welcome and the preferred way of accepting code contributions.

    Please follow these guidelines before sending a pull request:

    1. Update your fork to the latest upstream version.

    2. Use the develop branch to base your code off of. Create a topic-branch for your work. We will not merge your 'dev' branch, or your 'master' branch, only topic branches, coming from dev are merged.

    3. Follow the coding conventions of the original repository. Do not change line endings of the existing file, as this will rewrite the file and loses history.

    4. Keep your commits as autonomous as possible, i.e. create a new commit for every single bug fix or feature added.

    5. Always add meaningful commit messages. We should not have to guess at what your code is supposed to do.

    6. One pull request per feature. If you want multiple features, send multiple PR's

    Please follow this process; it's the best way to get your work included in the project:

    • Fork the project, clone your fork, and configure the remotes: