#git awareness
1 messages · Page 1 of 1 (latest)
ooh cool. feels a bit like? https://github.com/dagger/dagger/issues/8520
i guess the way i'd suggest solving this is by just adding more fields to the git api? and then we can just pass that object in with WithGit
not sure what those fields should be. maybe we should have GitRef.parent: GitRef to be able to traverse history.
we could also have GitRef.Diff: String to get the text diff of the given ref
i think that gives us the ability to do some more complex git stuffs
working on some of this now, since it's a pretty easy addition, and i'm in the area
will open something we can bikeshed around
There's also the relationship to the module system, eg. "run the tests on the current commit with and without staged changes"
😄 lol great minds
i'm thinking we add a GitRepo.Working that gives you the potentially dirty state of the git repo
i can add contextual git as well i think 🤔 will need to think through how, but can hack something together separately
i wanna get something for this soonish, since i want to write a code review agent for kubecon
for this i think contextual git is the call. i'm thinking we add a magic pragma, something like // +defaultGit will fill the arg with the current git state for that module
dunno, maybe there's something else we can do, but this feels "kinda right", and also very very easy to bolt in