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.
Can’t ya just git reset?
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.