22
33## Table of contents
44- [ Overview] ( #overview )
5- - [ Feature Requests] ( #feature-- requests )
6- - [ Bug Reports] ( #bug-- reports )
7- - [ Code Contributions] ( #code-- contributions )
5+ - [ Feature Requests] ( #feature-requests )
6+ - [ Bug Reports] ( #bug-reports )
7+ - [ Code Contributions] ( #code-contributions )
88
99## Overview
1010Thank you for wanting to contribute to this project.
@@ -27,9 +27,9 @@ Please go follow these steps to submit a bug:
2727- Create meaningful logs by:
28281 ) Switch decluttarr to debug mode (setting LOG_LEVEL: DEBUG)
29292 ) Turn off all remove functions but one where you expect a removal (example: REMOVE_STALLED: True and the rest on False)
30- 3 ) Let it run until the supposed remove should be trigged
30+ 3 ) Let it run until the supposed remove should be triggered
31314 ) Paste the full logs to a pastebin
32- 5 ) Share your settings (docker-compose or config.conf )
32+ 5 ) Share your settings (docker-compose or config.yaml )
33336 ) Optional: If helpful, share screenshots showing the problem (from your arr-app or qbit)
34347 ) Be responsive and provide more details if asked for them, and help testing the bug fix
3535
@@ -40,23 +40,23 @@ Code contributions are very welcome - thanks for helping improve this app!
40403 ) Only commit code that you have written yourself and is not owned by anybody else
41414 ) Create a PR against the "dev" branch
42425 ) Be responsive to code review
43- 5 ) Once the code is reviewed and OK, it will be merged to dev branch, which will create the "dev"-docker image
44- 6 ) Help testing that the dev image works
45- 7= Finally, we will then commit the change to the main branch, which will create the "latest"-docker image
43+ 6 ) Once the code is reviewed and OK, it will be merged to dev branch, which will create the "dev"-docker image
44+ 7 ) Help testing that the dev image works
45+ 8 ) Finally, we will then commit the change to the main branch, which will create the "latest"-docker image
4646
4747You do not need to know about how to create docker images to contribute here.
4848To get started:
49491 ) Create a fork of decluttarr
50502 ) Clone the git repository from the dev branch to your local machine ` git clone -b dev https://github.com/yourName/decluttarr `
51- 2 ) Create a virtual python environment (` python3 -m venv venv ` )
52- 3 ) Activate the virtual environment (` source venv/bin/activate ` )
53- 4 ) Install python libraries (` pip install -r docker/requirements.txt ` )
54- 5 ) Adjust the config/config.conf to your needs
55- 6 ) Adjust the code in the files as needed
56- 7 ) Run the script (` python3 main.py ` )
57- 8 ) Push your changes to your own git repo and use a descriptive name for the branch name (e.g. add-feature-to-xyz; bugfix-xyz)
58- 9 ) Test the dev-image it creates automatically
59- 10 ) Create the PR from your repo to ManiMatter/decluttarr (dev branch)
60- 11 ) Make sure all checks pass
61- 12 ) Squash your commits
62- 13 ) Test that the docker image works that was created when you pushed to your fork
51+ 3 ) Create a virtual python environment (` python3 -m venv venv ` )
52+ 4 ) Activate the virtual environment (` source venv/bin/activate ` )
53+ 5 ) Install python libraries (` pip install -r docker/requirements.txt ` )
54+ 6 ) Adjust the config/config.conf to your needs
55+ 7 ) Adjust the code in the files as needed
56+ 8 ) Run the script (` python3 main.py ` )
57+ 9 ) Push your changes to your own git repo and use a descriptive name for the branch name (e.g. add-feature-to-xyz; bugfix-xyz)
58+ 10 ) Test the dev-image it creates automatically
59+ 11 ) Create the PR from your repo to ManiMatter/decluttarr (dev branch)
60+ 12 ) Make sure all checks pass
61+ 13 ) Squash your commits
62+ 14 ) Test that the docker image works that was created when you pushed to your fork
0 commit comments