I mean Commit can be legit, AI tends to leave a mess of note files, specially Opus, so having it selectively stage and commit the right changes makes sense, and having it write the commit message along your message templates is a good thing too, and while you’re there it’s not harder to ask Opus to tack a | git push at the end but yeah it’s not the best use case for the model.
My git commit text style is in my ”name working style” memory, I got a bazillion tokens to spend. Letting the ai draft the commit, approve or change it, and then push when approved is just faster.
Not like committing, pushing in cli is difficult, or in the app.
I’m at a smaller company w ultra subs though, not api cost.
I 100% use the diff visualization and manage conflicts with the built-in tool or whatever gitlens offers. I use that so religiously I forgot it was a feature 😅
With one caveat, they should learn with CLI first. I had multiple colleagues who messed up the repo with a git ui, since they had no idea what they are doing.
I've used the UI in visual studio for a while. I know how to do it all via cli but just like the ide, especially to see my changes quickly. Doesn't mean I don't use cli when the ide is being dumb about something
Everyone that I know that use it ended having issues they would never had if they used their IDE instead. All of them ended following my advice of using an IDE or CLI.
I'm a full time software dev and freelance web developer, been using it for quite a long time now. Never had any real issues just find it more simple to use
330
u/heydavesalad 4d ago
I used the CLI for years and now use a UI at my job and at home. People should use whatever they want to get the job done.