Our current workflow for updating bank holidays is basically to curl the JSON at https://www.gov.uk/bank-holidays.json and commit it.
This is problematic, as the GOV.UK JSON only contains bank holidays from 5 years ago, and forward. If we want to make a timetable for, say, a 2015 election, we'll not be able to.
Rather than simply curling, we should make a script that grabs the data and merges it with the data we have already. We should seed this historic data with previous commits from this repo, to go back as far as we can (I think this is the oldest we have).
Our current workflow for updating bank holidays is basically to curl the JSON at
https://www.gov.uk/bank-holidays.jsonand commit it.This is problematic, as the GOV.UK JSON only contains bank holidays from 5 years ago, and forward. If we want to make a timetable for, say, a 2015 election, we'll not be able to.
Rather than simply curling, we should make a script that grabs the data and merges it with the data we have already. We should seed this historic data with previous commits from this repo, to go back as far as we can (I think this is the oldest we have).