Projected load shedding events that do happen aren't removed from the calendar about eskom-calendar HOT 1 CLOSED

I think I know what happened here, and it's two-fold:

1. Unfortunately keeping track of the loadshedding schedule is a manual process. If you submit a commit to update manually_specified.yaml, then this workflow will be triggered, which will recompile all the calendars and publish them again. Once this occurs, your calendar application should pull down the new information and update your calendar accordingly.

   The issue here is the manual updating part. Anyone can make changes to manually_specified.yaml, but so far I'm the only one so if I miss an update then things get out of date until I fix them. An example commit would be this one.

2. The other issue is that we recently didn't have any loadshedding scheduled (although at the time of writing this might change it seems). I hadn't actually checked the proper YAML specification, so I incorrectly specified an empty list which then caused the build to fail, which caused the calendars to not get updated. I've just fixed this issue with this commit.

So everything should be fixed now and your calendar should be up-to-date. Feel free to re-open if that's not the case!

from eskom-calendar.