4 ms·
I’ve had the same thought, but after playing around with it, it just seems like adding noise. I never find myself looking at generated code and wondering “what
by mock-possum 8mo ago
I’ve had the same thought, but after playing around with it, it just seems like adding noise. I never find myself looking at generated code and wondering “what prompt lead to that?” There’s no point, I won’t get any kind of useful response - I’m better off talking to the developer who committed it, that’s how code review works.
- what 8mo agoThe developer that committed won’t know because they didn’t write it… You can avoid the noise with git notes. Add the session as a note on the commit. No one has to read them if they’re not interested.
- mock-possum 8mo ago> The developer that committed won’t know because they didn’t write it… But they did commit it. I don’t really care who wrote it, if your account is on the commit, then you’re on the hook for the contents. If you can’t explain your own work, then I’m not really interested in collaborating with you.