last commit mismatch

### Are you experiencing an issue with...

shields.io

### 🐞 Description

I have some mirrors of gitlab repos, and as quick check to see if they're sync I thought I could use Shields.io badges to do so.

Unfortunately, in a few cases the last commits are out of sync (not in the actual mirror though). Of the 6 repos I'm mirroring, only 2 have a mismatch in the badge values.

Name
Upstream Repo
Mirror




libxcvt












Simple-Web-Server












wayland-protocols












wlr-protocols












xauth












xserver

For the wlr-protocols mirror (GitHub), it was clearly updated 5 months ago (October 2024), so not sure why the badge is showing March 2023.


For the xserver mirror (GitHub), it was also clearly updated 5 days ago (Last Friday), but this one only shows the month (March). I don't know if the GitHub last commit badge gets as granular as the Gitlab one.


### 🔗 Link to the badge

Name
Upstream Repo
Mirror




wlr-protocols












xserver

- https://img.shields.io/gitlab/last-commit/wlroots%2Fwlr-protocols?gitlab_url=https%3A%2F%2Fgitlab.freedesktop.org&style=for-the-badge&logo=gitlab
- https://img.shields.io/github/last-commit/LizardByte-infrastructure/wlr-protocols?style=for-the-badge&logo=github
- https://img.shields.io/gitlab/last-commit/xorg%2Fxserver?gitlab_url=https%3A%2F%2Fgitlab.freedesktop.org&style=for-the-badge&logo=gitlab
- https://img.shields.io/github/last-commit/LizardByte-infrastructure/xserver?style=for-the-badge&logo=github

### 💡 Possible Solution

Unsure.

No source files or tests are named. Reproduce the GitHub and GitLab last-commit badge URLs shown in the issue, then trace the corresponding badge handlers and provider responses to determine whether the mismatch is in repository data, date parsing, or rendering. Done means the affected mirror badges report the expected commit date and existing behavior remains covered by tests.

Written by the indexing model from the issue text.