.. i wish you hadn't made me look. That is painful.

A prompt for touching up those commit messages would be awesome!

PyCharm has local history that tracks non commit diffs and it has saved my day many times

If you want to quickly iterate through the commits and changes, you can do so with this link:

https://public-001.gitsense.com/insights/github/repos?p=comm...

Click on a file to bring up the diffs browser.

Disclaimer: I'm the creator of the tool that I'm linking to.

Looks like they are auto-generated on every save.

Had a co-worker once whose commits in Perforce (where it's called "Submit") made us joke that he had probably bound Ctrl-S to "Submit". Apparently it wasn't as unlikely as we thought .

Interesting to see someone doing this, it often comes up that we should actually have more levels of version control granularity than merges and commits. Just need an application of AI to generate good commit messages here :)

I use the "undo" functionality in my editor. In emacs it's a complete tree of changes so you can't really lose anything.

It's something but it's ephemeral and not shareable. You can't reconstruct how a piece of code got written weeks later, to eg recover some debug helpers you deleted without committing because you thought you were done with debugging it.

But thanks for the tip about Emacs undo tree, didn't know about that. With some add-ons you can apparently eg find undoable changes for only some region of a buffer, etc.

> With some add-ons you can apparently eg find undoable changes for only some region of a buffer, etc.

This is built into Emacs (no add-ons needed). Calling undo with a region selected undoes changes only in that region.

You can also setup undo-tree to show a diff for every change.

True, but that's no guarantee you'll ever be able to actually find it.

That could be interesting but the right structure (off the top of my head) would be a hierarchical layer - not this flat monstrosity!

I actually disagree with this because I think you should try to have the project even vaguely work at each commit, so "git bisect" will work. But maybe each commit could be a log of keystrokes instead of a text diff.

What a terrifying way to work!

Why? I also use commit and push as my save with nonsense commit messages. I can't trust that my computer is still booting up tomorrow.

For single author projects it's reasonable.