Home page does not get updated automatically

[jeromegv]

Hi

The "upcoming events" are still the December hacknights, not the January ones, not sure if the data exists for January but at the minimum December should not be showing as "upcoming"

I briefly mentioned it to Jordy in person and he mentioned that its just a job that has not run in a while.
I can see that this job here hasn't run since December 9th, it would likely need to be automated:
Build and Deploy Jekyll to GitHub Pages
https://github.com/CivicTechTO/civictech.ca/actions/workflows/pages.yml

[jordyarms]

@Khasir feel free to jump in if you have capacity.

[jordyarms]

update action

I've updated the archive with data for the upcoming hacknight, PR #53

This PR was created up https://github.com/CivicTechTO/civictech.ca/actions/runs/20449239015
Which when approved did run Build and Deploy Jekyll to GitHub Pages
https://github.com/CivicTechTO/civictech.ca/actions/runs/20470159938

---

current workflow configuration

update-submodule.yml runs on a cron basis daily, assessing changes to the archive.

When there is a change it triggers the change and generates a PR that then needs to be reviewed before building to production.

I had it set up without this approval step prior, but we've since implemented better controls on the main branch to prevent accidental or intentional blunders.

---

refinement of problem statement

There is no automated rebuild of the site based on lagging temporal display information in the build artifact. As the archive files themselves have not changed there is no trigger to indicate a new rendition of the site is required or that the display information is stale.

This could be resolved through the archive being updated regularly so that changes are reflected in new builds, or through automatically triggering a build on Wednesday mornings after the Tuesday events have occurred. The automation of a build on Wednesday will consume resources needlessly, but could be a sufficient solution.

Alternatively, a maintain can use the github interface to manually retrigger the build of the site if they observe the site is displaying stale information. This would avoid additional complexity or resource consumption, but is not automated.