New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Issue 36 🚨 shellcheck'ed #37
Conversation
Thanks for checking. I need to to look at this properly, but improvements are always welcome |
Please be patient. I need some time to test it locally. If it works, I'll merge it. In principal, there is nothing that stands against it - it's just a matter of time. |
There are still some un-resolved suggestions - did you miss those or was there a reason you did not include them?
at the beginning instead of fixing the issues? |
To be honest: I'm lacking time and some of these checks are more difficult to fix 🤷🏻♂️ |
No need to rush. It's done when it's done. I've installed shellcheck locally and hope to avoid such a mess in the future |
A local installation/container might be sufficient, but I sometimes forget in a hurry to check locally and I'm thankful for having a GitLab CI pipeline job for my (private) GitLab repos with this
If you don't know how to do this - I might also make a PR for you if I find out how this works on GitHub (just because I also want to know HOW to do this) 😁 |
I couldn't go to bed before I didn't know how GH action can handle this 😉 |
@yubiuser , please review my additions. Thanks :) |
Please do not always force-push. This conceals what has changed in each commit. Please just do a normal push |
Ok, I saw your recommendation after my last force-push. I pledge to do better 🙏🏻 |
…ned a string. adapt suggestion Co-authored-by: yubiuser <ckoenig@posteo.de>
Co-authored-by: yubiuser <ckoenig@posteo.de>
Co-authored-by: yubiuser <ckoenig@posteo.de>
Co-authored-by: yubiuser <ckoenig@posteo.de>
Co-authored-by: yubiuser <ckoenig@posteo.de>
Co-authored-by: yubiuser <ckoenig@posteo.de>
I created a new branch I hope to finish review for this today. |
Sounds great (dev-branch and the rest, too) 👍🏻 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Except of these two comments, the code looks fine now.
However, I've not tried it yet. Did you run the script - does it break something?
Yes, I did test it with all commits. Here are my final test results with Running outside docker container:
Running inside docker container:
|
The strange thing is: there is also text missing... it should continue with "(patially different) adlists in your gravity database." See my comment below, why it is failing. |
BTW: if we will come to a happy end, do you like to have a "clean" git history with only one rebased commit to commit fa8e5ba ? |
I think I will do a squash merge :) |
Co-authored-by: yubiuser <ckoenig@posteo.de>
Current running
|
So no real differences ;-) |
This fixes and closes issue #36.
I checked/validated by running
pihole_adlist_tool -d 1 -t 10 -u -a
with old and new version and diff'ed the results:For privacy reasons I can't get you full output. Maybe you can check this with your Pi-Hole… 🤔