I Time-Traveled My GitHub Commits… and It Actually Worked!

[Nisarg155]

Select Topic Area

Question

Body

Out of curiosity, I manually modified the commit dates and author info in my repo before pushing it to GitHub. And guess what? GitHub accepted it without any warnings—even future-dated commits showed up as if they were legit.

🔗 Repo for reference: https://github.com/Nisarg155/Temp

Things I Noticed:

• GitHub doesn’t verify if commit dates make sense—you can backdate or future-date them however you want.
• You can also modify the author info before pushing, meaning commits can appear under different names.
• The commit history now makes it look like I coded from the future.

Should GitHub Prevent Fake Commit Dates?

• Should GitHub flag or warn about unrealistic commit timestamps?
• While this isn't really a concern in shared repositories (since all contributors see the real commit history), it's interesting that commit dates aren’t strictly enforced.
• Or is this just how Git is meant to work, since it’s all decentralized?

I’m curious—what do you all think? Should GitHub do something about this, or is it fine as is?

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬