top | item 27581241 (no title) prisonality | 4 years ago > Git should store the commands that "did" the operations on a repo.is `git reflog` not enough for your use case ? discuss order hn newest pjettter|4 years ago No, I mean more like an audit trail. Not like `blame` either. What I typed on the command line to get into a new state. sixstringtheory|4 years ago What about `history | grep “^git”?Edit to add: the downside is that it only works in the current terminal session. To workaround that for myself, I have a fish shell post exec function that records the last command run, plus a bunch of metadata, to a log file.
pjettter|4 years ago No, I mean more like an audit trail. Not like `blame` either. What I typed on the command line to get into a new state. sixstringtheory|4 years ago What about `history | grep “^git”?Edit to add: the downside is that it only works in the current terminal session. To workaround that for myself, I have a fish shell post exec function that records the last command run, plus a bunch of metadata, to a log file.
sixstringtheory|4 years ago What about `history | grep “^git”?Edit to add: the downside is that it only works in the current terminal session. To workaround that for myself, I have a fish shell post exec function that records the last command run, plus a bunch of metadata, to a log file.
pjettter|4 years ago
sixstringtheory|4 years ago
Edit to add: the downside is that it only works in the current terminal session. To workaround that for myself, I have a fish shell post exec function that records the last command run, plus a bunch of metadata, to a log file.