fix: 2025 Council Pack 3

[m26dvd]

Fixing the following councils
fix: #1139 - Swale Borough Council
fix: #1192 - Midlothian Council
fix: #1179 - Newcastle City Council
fix: #1175 - Cardiff Council
fix: #1145
fix: #1127
fix: #890

Adding support for the following councils:
fix: #1180 - Boston Borough Council
fix: #1178 - Leicester City Council
fix: #1052 - East Staffordshire Borough Council
fix: #1083
fix: #1171 - East Lothian Council

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.93%. Comparing base (c662fed) to head (fd52b79).
Report is 21 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1197   +/-   ##
=======================================
  Coverage   71.93%   71.93%           
=======================================
  Files           9        9           
  Lines        1037     1037           
=======================================
  Hits          746      746           
  Misses        291      291           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[robbrad]

@m26dvd : can you rebase off master to pullin the latest workflow files ?

[m26dvd]

@robbrad I'll keep this one open if you need to test any further

[robbrad]

@m26dvd any chance you could try again on this test - rebase make a small change and commit/push ?

[m26dvd]

@robbrad Still the pesky Deploy Reports issue!

[robbrad]

@robbrad Still the pesky Deploy Reports issue!

I just can't get past this issue

It works if I run it but from PRs from other forks it does not.

Also strange but the PAT says it's never been used when it has

[robbrad]

@m26dvd Can you please try again mate?

[m26dvd]

@robbrad Still erroring unfortunately

[geekball]

@robbrad , I think it's permissions in the workflow (not an expert as use Azure DevOps at work), Did a bit of google digging and found:
(From: https://stackoverflow.com/questions/72851548/permission-denied-to-github-actionsbot)
permissions:
contents: read
pages: write # <-- Add this line

Looks like that pages: write should go around line 207/208 in the workflow since you're pushing to github pages?

[robbrad]

Last time please @m26dvd ! thank you 💯

[robbrad]

@robbrad , I think it's permissions in the workflow (not an expert as use Azure DevOps at work), Did a bit of google digging and found: (From: https://stackoverflow.com/questions/72851548/permission-denied-to-github-actionsbot) permissions: contents: read pages: write # <-- Add this line

Looks like that pages: write should go around line 207/208 in the workflow since you're pushing to github pages?

@m26dvd / @geekball

Yeh I tried that however its the commit to the branch that it does not like it looks like its inherent to GH not allowing the workflow to run from forks

Instead I have moved the reports from Allure (which is a shame cos they were nice to codecov)

I will update the documentation once I confirm it works

Here is an example of how they look - pretty nice cos on the PR you now get feedback on the failed test