-
Notifications
You must be signed in to change notification settings - Fork 49
Description
I've been exploring this for my dev workflows for https://github.com/axsaucedo/kaos. I have found that due to the nature of the repo, given there's often changes that involve multiple services, as well as context important context from previous commits (ie a commit in isolation may not be coherent outside of the bigger picture).
However I found that it's super useful when I run it with roborev review --branch-like approach on the respective worktree every time that an agentic loop finishes, which often would include a joint set of commits that are interlinked, and that also involve fixes that are tested running the integration tests (these take 4-5 mins so require being run at the end vs every commit).
For this I would find it quite useful if we could do a similar roborev init but extend with something along the lines of --hook-level agent|repo where agent would have the commit hook of running roborev for all commits until HEAD at once.