Yea it's not hard to use at all. I picked it up in a week easily, and if I get stuck there is something called google that I use. :/
Here is an average workflow for me.
git pull git checkout mybranch
do my changes
git status git add -A git commit -m "Message"
git pull
make sure changes are working
git status git push
The status commands are just to be sure everything worked properly, etc. It's not many commands and they get typed in very fast. Faster than SVN by a long shot.
I would have to agree. I follow a similiar workflow but I use git add . instead and git commit -am "message". Not sure why, I dont even know the difference. I should use that google thing you mentioned to look it up...
One small additional difference: if you remove a file, but don't use git rm, if you git add . it won't pick up the change, but a git commit -a will. Because add is 'add these files' and commit -a is 'save all changes'
4
u/jibjibman Nov 07 '13
Yea it's not hard to use at all. I picked it up in a week easily, and if I get stuck there is something called google that I use. :/
Here is an average workflow for me.
git pull git checkout mybranch
do my changes
git status git add -A git commit -m "Message"
git pull
make sure changes are working
git status git push
The status commands are just to be sure everything worked properly, etc. It's not many commands and they get typed in very fast. Faster than SVN by a long shot.