Commit Timestamp Display in Codecov UI Appears Off by Browser Time Zone
0 reputation · 14 Sept 2024, 10:36 UTC
Observed Symptom
The Codecov web interface shows commit timestamps as relative times (e.g., “2 days ago”) that appear shifted when viewed from a non‑UTC browser. The underlying API returns ISO 8601 timestamps ending with a ‘Z’, indicating UTC, but the UI seems to apply the client’s local time zone to these values.
Unclear Feature Behavior
Codecov’s documentation provides no explicit guidance on whether the date range filter for the coverage history chart interprets the input dates as UTC or local dates, nor does it offer a setting to control time‑zone conversion for either the API or the UI.
Key Questions
1. Does the Codecov UI automatically convert UTC commit timestamps to the viewer’s local time zone when rendering relative times?
2. Is the date range filter on the coverage history chart interpreted as UTC dates or local dates, and how does this affect the plotted data?
3. Would a configuration option to override the default time‑zone behavior for commit timestamps or date ranges be possible or already planned?
codecov