Home / FAQ

Frequently asked questions

Common questions about changing git commit dates, author metadata, and rewriting branch history with git-edit-date.

How do I change git commit dates?

Install git-edit-date, export the branch to CSV, edit author_date and committer_date in a spreadsheet, then run apply. Works for the last commit too — edit one row in the CSV. Follow the tutorial or the guide to change the last git commit date.

How do I bulk-edit git commit dates on a branch?

Export your branch history to CSV with git-edit-date export, edit author_date and committer_date in a spreadsheet, then run git-edit-date apply. See the tutorial.

What is the difference between author date and committer date?

Author date is when the work was originally done. Committer date is when the commit object was written to the repository. git-edit-date lets you set both independently via CSV. Deep dive: author date vs commit date.

Does git-edit-date change commit messages?

No. The message column in the CSV is for reference only. Apply updates author name, author email, author date, and committer date — not messages.

Will GPG signatures break?

Yes. Rewriting history creates new commit objects with new SHAs. Any GPG signatures on the original commits become invalid and must be re-signed if you need signed commits.

Can I edit only some commits?

Yes. Leave rows unchanged if you only want to fix specific commits. The tool rewrites the full branch history but only applies the metadata changes present in your CSV.

Is it safe to rewrite shared or protected branches?

Generally no. History rewrites disrupt collaborators and can violate branch protection rules. Use git-edit-date on personal or feature branches, coordinate with your team, and never force-push to main without explicit agreement.

Do I need git filter-branch?

No. Use git-edit-date for branch-level date fixes via CSV — export, edit timestamps in a spreadsheet, apply once.

Excel vs LibreOffice — any CSV gotchas?

Export uses double-quoted CSV fields so commas and newlines in messages stay safe. Save as CSV, not XLSX. Keep RFC3339 date format with timezone offset. Do not edit the hash column.

Do I need to force push?

If the branch was already pushed, yes — commit SHAs change after a rewrite. Use git push --force-with-lease instead of bare --force. It refuses to push if someone else updated the remote since your last fetch.