How do I check the date and time of the latest `git pull` that was executed?
GitGit PullGit Problem Overview
How do I check the date and time of the latest git pull
that was executed? I frequently need to know when the code changed on a server when something goes wrong.
Git Solutions
Solution 1 - Git
stat -c %Y .git/FETCH_HEAD
Will give you a unix timestamp of the last modification of that file. Git writes the FETCH_HEAD file every time you pull or fetch, even if there was nothing to pull.
Solution 2 - Git
On a hunch, I tried "stat -c %y .git/FETCH_HEAD", and got a human-readable printout of the time:
> stat -c %y .git/FETCH_HEAD
2015-02-24 17:42:08.072094410 -0500
Furthermore, you can add
when = !stat -c %y .git/FETCH_HEAD
to the [alias]
section in your ~/.gitconfig file (it's safest to do this automatically by running the following command line in any git repo)
git config --global alias.when '!stat -c %y .git/FETCH_HEAD'
and then you are able to find this info with your new "command", anytime:
> git when
2015-02-23 15:07:53.086254218 -0500
[Then it occurred to me to do "man stat", and I found that there are a bunch of other %
Solution 3 - Git
The git show
command shows the date of the most recent commit. This isn't the date at which the commit was pulled to the local repository, but Git doesn't keep such pull information.
You may be able to find the time of the last pull using the ctime (creation time) of the files on the server. For example:
ls -lct
shows the ctime of each file, sorted with the most recent first.
Solution 4 - Git
git show -1 --stat
>This git command shows the latest changes commits time and date with message
Solution 5 - Git
In a non-bare repository (and a bare repository doesn't make sense for git pull
), git logs all changes to branch tips and the current branch idea in "reflogs", in .git/logs
. You can view these using git log -g
.
However, although the log files do have timestamps, it doesn't appear that git log -g
will print it. However, if you take a look at .git/logs/HEAD
for example, you'll see that the format is quite simple to parse- it consists of what the ref (or HEAD) changed from, changed to, who changed it, when and an activity message.
Solution 6 - Git
Use python: python -c "import os;print os.stat('.git/FETCH_HEAD').st_mtime"
Solution 7 - Git
python -c "import os, datetime ;print datetime.datetime.fromtimestamp(os.stat('.git/FETCH_HEAD').st_mtime)"
or
python3 -c "import os, datetime ;print(datetime.datetime.fromtimestamp(os.stat('.git/FETCH_HEAD').st_mtime))"
Solution 8 - Git
Cross Platform (OSX/Linux) Bash Solution
Heavily inspired by @smooves
answer: https://stackoverflow.com/a/9229377/622276 and comments.
But I am maintaining my own bash prompt git integration
With the source here: https://github.com/neozenith/dotfiles/blob/master/bash-scripts/function_parse_git_prompt.sh
msys
version in Git Bash for Windows works identical to the linux version.
I'm compiling the cross platform options into a case statement. So it will fork a fetch process on any git repo I navigate into that is older than fifteen minutes since last fetch so the rest of my prompt script knows if I have stuff to pull.
Git radar used to to this but it required saving a file with timestamp of when the last fetch was called. This writes no temporary files.
git rev-parse --show-toplevel
just means if I'm anywhere in a git repo it will get the repo root so we can reference the .git
folder path.
# No repo == no more work
local REPO_ROOT=`git rev-parse --show-toplevel 2> /dev/null`
if [[ -n $REPO_ROOT && -e "$REPO_ROOT/.git/FETCH_HEAD" ]]; then
case $OSTYPE in
darwin*)
local LAST_FETCH="$(stat -f '%m' $REPO_ROOT/.git/FETCH_HEAD)"
local FETCH_THRESHOLD="$(date -v-15m +%s)"
;;
*)
local LAST_FETCH="$(stat -c %Y $REPO_ROOT/.git/FETCH_HEAD)"
local FETCH_THRESHOLD="$(date -d'15 minutes ago' +%s)"
;;
esac
# Fork fetch process in background
if [[ $LAST_FETCH -lt $FETCH_THRESHOLD ]]; then
git fetch --all --quiet --prune 2> /dev/null &
fi
fi
Solution 9 - Git
Here's a small git wrapper. Install it with the name git
and with rights chmod a+x git
. Then add last_successful_fetch
to .git/info/exclude
.
When you want to see the result, use stat last_successful_fetch
.
#!/bin/sh
# This script just invokes git as expected, plus one additional action:
# If there stands last_successful_fetch in .git/info/exclude, then
# this file will be touched in top dir.
"`which --all git | uniq | head -n 2 | tail -n 1`" "$@"
status=$?
if [ _"$1" = _pull -o _"$1" = _fetch ]; then
if grep last_successful_fetch "`git rev-parse --git-dir`/info/exclude" >/dev/null 2>&1; then
[ $status = 0 ] && touch last_successful_fetch
fi
fi
Solution 10 - Git
$ # for the latest pull even if there's nothing new
$ stat -c %y .git/FETCH_HEAD
2017-12-15 11:24:25.000000000 +0100
$
$ # for records of updated references
$ git reflog --date=iso
db2bba84 (HEAD -> master, origin/master, origin/HEAD) HEAD@{2017-12-14 11:28:39 +0100}: pull: Fast-forward
37fe73ad HEAD@{2017-12-03 17:09:32 +0100}: pull: Fast-forward
c4107fcd HEAD@{2017-11-27 18:53:40 +0100}: clone: from https://github.com/macports/macports-base
$
$ # for a more detailed view of the latter
$ git log -g
commit db2bba84d5e8cd82ec94a19129deb91ef62287bb (HEAD -> master, origin/master, origin/HEAD)
Reflog: HEAD@{0} (me <me@machine.local>)
Reflog message: pull: Fast-forward
Author: Ryan Schmidt <ryandesign@macports.org>
Date: Wed Dec 13 10:23:47 2017 -0600
portutil.tcl: Fix renames that supply the -force option
Treat $options as a list not as a string.
See: https://trac.macports.org/ticket/55492
[snip]
Solution 11 - Git
In my case I had to go back to get the second to last pull (previous-1), so used this reflog command, note that reflogs expire in 90 days by default. Hope this will be helpful to someone.
master ± -> git reflog --date=iso|grep pull
67718cc11 HEAD@{2022-01-25 10:14:31 +0530}: pull: Fast-forward
9bb64364a HEAD@{2021-12-13 18:22:17 +0530}: pull: Fast-forward
f5cf7c887 HEAD@{2021-11-29 13:08:14 +0530}: pull: Fast-forward
then you can checkout that hash and create a branch. (detached head in below command)
git checkout 9bb64364a
Solution 12 - Git
As suggested by user: https://stackoverflow.com/users/83646/smoove, you can find when git pull was last called on the repo by checking the modification timestamp of: .git/FETCH_HEAD as: git writes the .git/FETCH_HEAD file every time you pull or fetch, even if there was nothing to pull.
Example: {master} vinegupt@bhling69(/imsgit_local/work/vinegupt/ims_18.5a/ims_common)$ stat -c %y .git/FETCH_HEAD
2018-02-12 02:01:50.487160386 +0530