fix: Various council fixes

[dp247]

Fixes scrapers for the following councils:

• Basingstoke
• Bath & North East Somerset
• Blackburn
• Malvern Hill
• Swale

Two new dependencies have been added to the TOML as some of them needed custom HTTP handlers to avoid SSL errors.

[robbrad]

Hmm looks like it failed the lint commit 🫣 @dp247

I need to try this for myself

[dp247]

Oh no

[dp247]

Should I have a subject and type in every commit message? @OliverCullimore

Maybe that's where I'm going wrong 🤣

[OliverCullimore]

@dp247 @robbrad Yes, each one of those commit messages should've have "fix:" at the start, then your normal message (what it calls subject).

[OliverCullimore]

@dp247 There's a few ways you can resolve this:

• Un-commit then recommit your last commit with a message with the "fix:" prefix added to the start (this is what I did for you from my IDE for the last PR)

• Make another change of some kind and commit it with the "fix:" prefix your the commit mesage

• Ignore the lint errors and merge the PR, it just won't create a realease so the fixes will appear the next time a commit with the right prefixes is merged

[dp247]

@dp247 There's a few ways you can resolve this:

• Un-commit then recommit your last commit with a message with the "fix:" prefix added to the start (this is what I did for you from my IDE for the last PR)
• Make another change of some kind and commit it with the "fix:" prefix your the commit mesage
• Ignore the lint errors and merge the PR, it just won't create a realease so the fixes will appear the next time a commit with the right prefixes is merged

Thanks for the tips - I'm gonna fix some more so I'll make sure I preface them correctly 🙏

[codecov-commenter]

Codecov Report

Merging #361 (212d859) into master (7e2b723) will not change coverage.
The diff coverage is n/a.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

@@           Coverage Diff           @@
##           master     #361   +/-   ##
=======================================
  Coverage   83.44%   83.44%           
=======================================
  Files           3        3           
  Lines         151      151           
=======================================
  Hits          126      126           
  Misses         25       25           

[OliverCullimore]

@dp247 that commit message is looking good 🙌

The lint action will still be erroring because of the previous commits in this PR but that can just be ignored now you've added one with the prefix that will trigger the release 🙂

[dp247]

@dp247 that commit message is looking good 🙌

The lint action will still be erroring because of the previous commits in this PR but that can just be ignored now you've added one with the prefix that will trigger the release 🙂

Thank god, I was worried I'd have to bring out command line Git to amend them all hehe 🤣

[OliverCullimore]

@dp247 these fixes look good, are you still working on any further changes for this PR or can it be merged now?

[dp247]

@dp247 these fixes look good, are you still working on any further changes for this PR or can it be merged now?

You can merge these for now - I might do a few more today but can always open a new PR