Release Heroku support (Sourcery refactored)

[sourcery-ai[bot]]

Pull Request #41 refactored by Sourcery.

If you're happy with these changes, merge this Pull Request using the Squash and merge strategy.

NOTE: As code is pushed to the original Pull Request, Sourcery will re-run and update (force-push) this Pull Request with new refactorings as necessary. If Sourcery finds no refactorings at any point, this Pull Request will be closed automatically.

See our documentation here.

Run Sourcery locally

Reduce the feedback loop during development by using the Sourcery editor plugin:

• VS Code
• PyCharm

Review changes via command line

To manually merge these changes, make sure you're on the heroku_test branch, then run:

git fetch origin sourcery/heroku_test
git merge --ff-only FETCH_HEAD
git reset HEAD^

Help us improve this pull request!

[sourcery-ai[bot]]

Sourcery Code Quality Report

✅  Merging this PR will increase code quality in the affected files by 1.48%.

Quality metrics	Before	After	Change
Complexity	20.98 😞	18.98 😞	-2.00 👍
Method Length	134.44 😞	132.56 😞	-1.88 👍
Working memory	12.23 😞	12.13 😞	-0.10 👍
Quality	42.44% 😞	43.92% 😞	1.48% 👍

Other metrics	Before	After	Change
Lines	371	366	-5

Changed files	Quality Before	Quality After	Quality Change
hikka/modules/test.py	42.44% 😞	43.92% 😞	1.48% 👍

Here are some functions in these files that still need a tune-up:

File	Function	Complexity	Length	Working Memory	Quality	Recommendation
hikka/modules/test.py	TestMod.logscmd	40 ⛔	560 ⛔	15 😞	14.34% ⛔	Refactor to reduce nesting. Try splitting into smaller methods. Extract out complex expressions
hikka/modules/test.py	TestMod.debugmodcmd	12 🙂	156 😞	14 😞	44.18% 😞	Try splitting into smaller methods. Extract out complex expressions
hikka/modules/test.py	TestMod.client_ready	4 ⭐	151 😞	15 😞	50.96% 🙂	Try splitting into smaller methods. Extract out complex expressions
hikka/modules/test.py	TestMod.watchdog	8 ⭐	123 😞	8 🙂	62.43% 🙂	Try splitting into smaller methods

Legend and Explanation

The emojis denote the absolute quality of the code:

• ⭐ excellent
• 🙂 good
• 😞 poor
• ⛔ very poor

The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request.

---

Please see our documentation here for details on how these metrics are calculated.

We are actively working on this report - lots more documentation and extra metrics to come!

Help us improve this quality report!