mandel_x
Re:If AI writes code, should the session be part of the commit?
on Monday March 02, 2026 @12:25AM (#47214182)
> people have been submitting so many Show HNs of generated projects
In this case, it was more of write the X language compiler using X. I had to prove to myself if keeping the session made sense, and what better way to do it than to vibe code the tool to audit vibe code.
I do get your point though
Re:If AI writes code, should the session be part of the commit?
on Monday March 02, 2026 @12:16AM (#47214115)
You are 100% and that’s why I chose git notes. If you do not sync them you have no knowledge of their existence.
Re:If AI writes code, should the session be part of the commit?
on Sunday March 01, 2026 @10:09PM (#47213404)
I added an action that will add a comment with the notes in GitHub so that you can see them directly.
I did work around squash to collect all sessions and concatenate them as a single one
Re:If AI writes code, should the session be part of the commit?
on Sunday March 01, 2026 @07:44PM (#47212477)
People won’t do that, unfortunately. We are a dying breed (I hate it). I went against my own instincts and vibe code this, works as a proof of concept.
You can see the session (including my typos) and compare what was asked for and what you got.
Re:If AI writes code, should the session be part of the commit?
on Sunday March 01, 2026 @07:27PM (#47212356)
I’ve been thinking about a simple problem:
We’re increasingly merging AI-assisted code into production, but we rarely preserve the thing that actually produced it — the session.
Six months later, when debugging or reviewing history, the only artifact left is the diff.
So I built git-memento.
It attaches AI session transcripts to commits using Git notes.