The timestamp for the "Updated" field of an issue is misleading

[stevenvdb]

On 2023-07-13 09:39, the page for incident 57 looks as follows:

---

Unexpected shutdown of Tier-1 nodes due to cooling issues

Start:	2023-07-12 12:31:00
End:	Unknown
Updated:	2023-07-13 09:21:54
Level:	high

The majority of Tier1 nodes has shut down due to an unexpected temperature rise.

Minor works to the cooling system by the vendor seemingly have impacted the Tier1 system.

We are investigating what is going on and how soon the system can come back up again.

---

The last update of the content of this incident was however on 2023-07-12 (#83), and not 2023-07-13 09:21:54 as the table above suggests. I assume that timestamp just refers to the last automated deployment. I think it would be better if the timestamp of the "Updated" field would actually show the last time the content for the incident was updated.

[RVerschoren]

This seems to be a bug with the automated deployment rather than intended behaviour.

The corresponding code itself (function get_modification_date in scripts/incident_parser.py) uses git --no-pager log --format=%ci <incident_filename> to get the last modification date in git, falling back to the last modification OS timestamp.

When I execute that git command on incidents/hortense_20230712.yml or render the website locally (scripts/render_site.py), I get 2023-07-12 13:17:18 for that incident.