Git Commit Date Generator

Most used Git commands

Quick reference for common Git commands. Replace placeholders like <file_path> or <branch_name> with your values.

How it works

This tool generates the exact Git commands you need to change git commit date and set both author and committer timestamps. Use it when you want to backdate commit history, fix timezone mistakes, or align your GitHub contribution graph with the real dates you coded. Pick a date and time (and timezone), then copy the command for your shell—Bash, PowerShell, or CMD—and run it in your repository.

For the contribution graph and most tools, use the "Full Timestamp Forge (Sync)" command so both author and committer date match. After amending or creating a commit, use the generated force-push command to update the remote.

Frequently asked questions

How do I change the date of a Git commit?

Use this tool to generate the exact Git commands. Pick your desired date and time, then run the "Full Timestamp Forge" command in your repo. That sets both author and committer date so the commit appears with your chosen timestamp everywhere, including GitHub.

Why don't my GitHub contribution squares update?

GitHub uses the committer date for the contribution graph. If you only set the author date, the square won't change. Use the "Full Timestamp Forge (Sync)" command from this tool—it sets both GIT_AUTHOR_DATE and GIT_COMMITTER_DATE. After amending or creating a commit, force-push to update the remote.

What's the difference between author date and committer date?

Author date is when the change was originally made; committer date is when the commit was last applied (e.g. after a rebase or amend). Git log shows both. For backdating and for GitHub contributions, both need to match, which is what the Full Timestamp Forge command does.

Can I use this on Windows (PowerShell/CMD)?

Yes. The tool outputs commands for Bash, PowerShell, and CMD. Switch the shell tabs above the generated commands and copy the version for your environment.

Is it safe to change commit dates?

Changing dates only rewrites history locally. Pushing those changes requires a force push, which can disrupt others if they've pulled the same branch. Use it for personal or solo branches; coordinate with your team before rewriting shared history.