It might come to a situation where users have problems with the tooling and the program behaves different for other users. One reason might be working on an old commit. Therefore it would be useful if the notebook prints a message on which version the notebook is executed.
This information can either be retrieved using the git command line tool or from the git configuration. Within the .git/HEAD file is states the current branch. Then printing the info of the referenced file will tell the current commit hash.

$: cat HEAD
ref: refs/heads/feat/timeframes.  <--- file to look to the commit hash
$: cat refs/heads/feat/timeframes
bd084d728edfbc8bf34ff6accccf136c2c30e449   <-- commit hash