EzTerry

Well no human looked at it while coding, no human looked at it while testing, so should be good as long as no user is a human looking at it…

That’s not vibe coding… Its vibe testing…

Anything you can do in Jujitsu you can do in git… The big difference is a paradime change:

-instead of a working directory that has pending changes you need to add than commit, all changes are in a commit that is lacking metadata.

The system has better “editing” of local history to set that meta data. But once you push to a shared repo you run the usual risks of force pushing.

I’m not sold, rather git not do anything until asked and just run git status constantly but I don’t have first hand experience… I would theory it would be more likely to add a file you didn’t mean to… Unlike those who use windows guis for git and forget to add new files.

Funny those are commands I avoid… They all have to do with editing history which I know there is a vocal group here that loves “clean” history but that isn’t what happened.

sure merge full features so you can roll back a feature… And if something is really off I might start from a snapshot commit and cherry pick/merge a bunch in but usually history is histoy… If submitting to a public project I may make a new branch with the cleaned version but why edit in line. That is risking issues.

See now it’s saving 20 million /s