Jokes on you, I’ve used it to untangle messy git problems (with a backup of course).
Comment on Lutris now being built with Claude AI, developer decides to hide it after backlash
PrettyFlyForAFatGuy@feddit.uk 3 days agoIf it’s making commits for you you’re vibe coding.
I use it at work, I use it for troubleshooting and if I get it to generate anything for me, I stage them and review them before committing myself
fossilesque@mander.xyz 3 days ago
veniasilente@lemmy.dbzer0.com 2 days ago
You can do that with 99.9% less damage to the environment and the working class with
git -f rebase, or even the old tried and true method ofrm -rf && git pull ….fossilesque@mander.xyz 1 day ago
Not in my case I’m afraid.
veniasilente@lemmy.dbzer0.com 1 day ago
Oh you have to deal with the actually gnarly parts of git… sending my condolences.
r1veRRR@feddit.org 2 days ago
No, vibe coding explicitly requires NEVER looking at the actual code. I can give claude a ticket, it creates a plan. I review that plan, maybe change some things. Then claude does the thing. I review the code, then tell claude to fix X. Then I test, then I tell claude to create a commit.
There we have claude creating a commit without any of it being vibe coded
Auli@lemmy.ca 2 days ago
That is still vibe coding.