5 ms·

Side note but what is going on with this projects commits?

by exdsq 5y ago

globular-toast 5y ago
Looks like they are auto-generated on every save.
- lordgrenville 5y ago
  What a terrifying way to work!
  - IshKebab 5y ago
    For single author projects it's reasonable.
  - Kiro 5y ago
    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.
- fulafel 5y ago
  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 :)
  - exdsq 5y ago
    That could be interesting but the right structure (off the top of my head) would be a hierarchical layer - not this flat monstrosity!
  - globular-toast 5y ago
    I use the "undo" functionality in my editor. In emacs it's a complete tree of changes so you can't really lose anything.
    - tom_ 5y ago
      True, but that's no guarantee you'll ever be able to actually find it.
    - fulafel 5y ago
      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.
      - mssdvd 5y ago
        You can also setup undo-tree to show a diff for every change.
      - karthink 5y ago
        > 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.
  - astrange 5y ago
    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.
- simiones 5y ago
  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 .
adkadskhj 5y ago
.. i wish you hadn't made me look. That is painful.
- jimsimmons 5y ago
  PyCharm has local history that tracks non commit diffs and it has saved my day many times
- mullikine 5y ago
  A prompt for touching up those commit messages would be awesome!
sdesol 5y ago
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=commits&q=window%3A365&r=github%3Asemiosis%2Fpen.el&v=repo 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.

Side note but what is going on with this projects commits?

by exdsq 5y ago

Side note but what is going on with this projects commits?

globular-toast 5y ago

Looks like they are auto-generated on every save.

lordgrenville 5y ago
What a terrifying way to work!
- IshKebab 5y ago
  For single author projects it's reasonable.
- Kiro 5y ago
  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.
fulafel 5y ago
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 :)
- exdsq 5y ago
  That could be interesting but the right structure (off the top of my head) would be a hierarchical layer - not this flat monstrosity!
- globular-toast 5y ago
  I use the "undo" functionality in my editor. In emacs it's a complete tree of changes so you can't really lose anything.
  - tom_ 5y ago
    True, but that's no guarantee you'll ever be able to actually find it.
  - fulafel 5y ago
    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.
    - mssdvd 5y ago
      You can also setup undo-tree to show a diff for every change.
    - karthink 5y ago
      > 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.
- astrange 5y ago
  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.
simiones 5y ago
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 .

adkadskhj 5y ago

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

jimsimmons 5y ago
PyCharm has local history that tracks non commit diffs and it has saved my day many times
mullikine 5y ago
A prompt for touching up those commit messages would be awesome!

sdesol 5y ago

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=commits&q=window%3A365&r=github%3Asemiosis%2Fpen.el&v=repo 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.