Git Reference ยท Revisions and Pathspecs
Date formats in Git
Reference for dates in Git: accepted input forms (ISO 8601, RFC 2822, raw, relative), --date output formats, GIT_AUTHOR_DATE and --since expressions.
Git handles dates in two directions. Input: you give a date to --date, GIT_AUTHOR_DATE, GIT_COMMITTER_DATE, --since, --until or @{2.days.ago}. Output: you pick how git log, git show and git blame print dates with --date=<format> or the log.date setting. Internally every commit stores a Unix timestamp plus a time zone offset, such as 1700000000 +0100.
For input, Git has a forgiving parser called approxidate. It accepts strict forms (raw, ISO 8601, RFC 2822) and informal phrases such as yesterday, 3 weeks ago or last friday. Strict forms are the safe choice for scripts, because informal phrases depend on the current time and give different results from one day to the next.
GIT_AUTHOR_DATE="2024-03-05T10:00:00+0000" git commit -m "x" git log --since="2 weeks ago" --date=short git log --date=format:'%Y-%m-%d %H:%M' --format='%ad %s'
Try it
Press Run (or Ctrl + Enter) to see the result here.
Program input ยท what you'd type while the program runs
Type the answers before you press Run, one per line. Each time the program reads a line (with read or cat), it gets the next line from this box.
Press Run (or Ctrl + Enter) to see the result here.
Program input ยท what you'd type while the program runs
Type the answers before you press Run, one per line. Each time the program reads a line (with read or cat), it gets the next line from this box.
Syntax
Input formats
| Form | Example | Notes |
|---|---|---|
| Git internal (raw) | 1709649000 +0200 |
Unix seconds and a zone offset. Add @ in some contexts: @1709649000. |
| ISO 8601 | 2024-03-05T14:30:00+0100, 2024-03-05 14:30:00Z |
Best for scripts; the zone is respected. |
| RFC 2822 | Tue, 5 Mar 2024 14:30:00 +0100 |
The format used in email headers and patches. |
| Dotted / numeric | 2024.03.05, 03/05/2024, 5.3.2024 |
Month and day order follows the format shape; ambiguous numbers are guessed. |
| Relative (approxidate) | yesterday, 2.days.ago, last tuesday, noon yesterday |
Used mostly with --since, --until, @{...}. |
Output formats (--date=): default, local, iso (iso8601), iso-strict, rfc (rfc2822), short (date only), relative, human, raw, unix, and format:<strftime> or format-local:<strftime>. Modifiers -local (as in iso-local) convert to your current zone.
Errors and edge cases: an invalid date makes a commit fail with fatal: invalid date format. When no zone is given, the local zone of the machine is used, so equal text can mean different instants on different computers. --since with a vague phrase is evaluated relative to now, and git log --since=yesterday may not match when you run it twice a day apart.
Usage notes
- Reproducible commits. Set both
GIT_AUTHOR_DATEandGIT_COMMITTER_DATE(and the names) to get the same commit hash every time, which is why the examples on this site use fixed values. --dateon commit sets only the author date. The committer date still comes fromGIT_COMMITTER_DATEor the clock.git commit --amend --reset-authorrefreshes the author date to now.relativeandhumanchange with the clock. Avoid them in anything you compare or store. Useiso-strictorrawfor machine-readable output.- Time zones are part of the date.
isoshows the author's zone as written in the commit;localconverts it to yours. Two commits made at the same instant in different zones print different text. - Set a default with
log.date(see log.*); command-line--dateoverrides it. - Format placeholders: in
--format,%adhonors--date, while%aD(RFC 2822),%ai(ISO-like),%aI(strict ISO),%as(short),%at(Unix) and%ar(relative) are fixed styles; see git log --pretty. - Reflog selectors such as
main@{yesterday}orHEAD@{2.weeks.ago}use the same parser, but read your local reflog, not the commit dates; see @{n} and @{date}. - Year-less input like
Mar 5assumes the current year, and times in the future may be moved back into the past; add the year in scripts.