Post

hey @gitbutler.com I'm already really really missing gitbutler's CLI's ability to stage changes to certain lanes. I created a setup where different agents assign their changes via stop hooks over to dedicated lanes. I was very happy with it 🥲 Can i please have it back?

0 reposts0 likes

thats what i do now, theres some friction tho some of them: - moving staged changes around e.g. between lanes in order to resolve conflicts is much more lightweight than having to disect a _bunch_ of commits for individual hunks. - agent hooks triggering on stop now dictate the commit granularity..

instead of me, which requires additional manual commit cleanup if i want to create reviewer friendly logical commits. - unfortunately effectively losing the unstaged status for changes (when using an agent hook setup) now no longer plays nicely with e.g. codex review views

That being said I'm purely talking about convenience here. Everythings functional. Its just my setup that suddenly got 'less cool/convenient' overnight ¯\_(ツ)_/¯ My setup being heavily agent driven and stop hook utilization.

the same approach where agents can only commit directly makes retrospective changes so much harder / less convenient. I assume theres good reasons 'but' can no longer stage tho 😭..?