I actually believe we need to rethink Git for modern needs. Saving prompts and sessions alongside commits could become the norm for example, or I could imagine having different flags for whether a contribution was created by a human or not.
This doesn't seem to be the direction these guys are going though, it looks like they think Git should be more social or something.
Idk how git works under the hood but those both seem like they could both be easily accomplished with git itself .
but if not just your own work flow, have a dir dedicated to storing prompt history and then each file is titled with the commit id.
As for the flag just agree to some convention and toss it in the commit message
Actually, it is. We're currently leading a conversation among several players in this space to agree on a metadata standard that helps make attaching, collaborating on and transmitting information like this simple, extensible and scalable.
Keep an eye on our blog to see how we're doing this, and how we're doing it in a way that hopefully the entire community joins us in a way where we're not all reinventing the same wheels.
>Saving prompts and sessions alongside commits could become the norm for example, or I could imagine having different flags for whether a contribution was created by a human or not.
Yes, it could have syntax like
and then the tooling could attach any metadata to it that is desired.OH WAIT YOU CAN DO THAT ALREADY SINCE 2009
Seriously, the 90% complaints about git not being able to do something is just either RTFM or "well, it can, but could use some better porcelain to present to user"
> I could imagine having different flags for whether a contribution was created by a human or not.
Only useful if it can be reliably verified, which is challenging at best.
The point of git is that it has strong authentication built into the fabric of the thing.
What do people expect to do with these saved prompts/contexts? Nobody is going to read through them, right? I suppose the thinking is LLMs will, but any decently active codebase will soon contain far too much context for any current LLM. Is this the same thinking behind cryonics, ie. we may be able to use this stuff one day so let's start saving it now? Hoarding has ruined many people and it will ruin us all if we're not careful...
For me the reason would be to preserve traces of intentionality (ie what was the user trying to achieve with this commit?). These days a 10k LOC commit might be triggered by a 100-word user prompt, there is a lot more signal in reading the prompt itself than the code changes.
I mean, it's just text, so it shouldn't be too taxing to store it. I agree it's hoarder mentality though :)
remove the existing code, add feature to the prompt and re-generate everything, probably