Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

last commit mismatch #10960

Open
ReenigneArcher opened this issue Mar 19, 2025 · 2 comments
Open

last commit mismatch #10960

ReenigneArcher opened this issue Mar 19, 2025 · 2 comments
Labels
question Support questions, usage questions, unconfirmed bugs, discussions, ideas

Comments

@ReenigneArcher
Copy link

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 GitLab Last Commit GitHub last commit
Simple-Web-Server GitLab Last Commit GitHub last commit
wayland-protocols GitLab Last Commit GitHub last commit
wlr-protocols GitLab Last Commit GitHub last commit
xauth GitLab Last Commit GitHub last commit
xserver GitLab Last Commit GitHub last commit

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.

Image

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.

Image

🔗 Link to the badge

Name Upstream Repo Mirror
wlr-protocols GitLab Last Commit GitHub last commit
xserver GitLab Last Commit GitHub last commit

💡 Possible Solution

Unsure.

@ReenigneArcher ReenigneArcher added the question Support questions, usage questions, unconfirmed bugs, discussions, ideas label Mar 19, 2025
@chris48s
Copy link
Member

Fundamentally this is the difference between author timestamp and committer timestamp:

$ curl --silent "https://api.github.com/repos/LizardByte-infrastructure/wlr-protocols/commits?per_page=1" | jq 'map({author: {date: .commit.author.date}, committer: {date: .commit.committer.date}})[]'
{
  "author": {
    "date": "2023-03-18T19:24:44Z"
  },
  "committer": {
    "date": "2024-10-08T20:03:48Z"
  }
}

@ReenigneArcher
Copy link
Author

Thanks for looking into this.

I also noticed a mismatch with BitBucket. https://github.com/LizardByte-infrastructure#-mirrors

It would be nice if they could utilize the same logic between the different git backends. Not critical though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Support questions, usage questions, unconfirmed bugs, discussions, ideas
Projects
None yet
Development

No branches or pull requests

2 participants