Dirty!
My co-worker/underling/partner/intern (I haven't yet figured out the best way to refer to him when I can't use his name) are still in learning mode when it comes to git. At the end of last week, after mostly leaving my co-worker on his own for awhile, I noticed there were a fair amount of uncommitted changes on the 'master' branches of the repos we were doing most of our work in. A few were from me, as a left-over habit of my workflow using darcs where the 'system-of-patches' easily allowed committing (recording) of changes to just one portion of a file, while git requires all changes to a file to be recorded at once. Most were from my co-worker though, so I went ahead and created new branches where necessary and began committing for him. I created a 'gitcoj' alias to 'git commit --author="coworkers name that starts with a j<emailaddress@work.com>". Since I sometimes find myself wanting to commit while I'm sudo'd to root, I went ahead and added an alias to commit with me as author, and staying consistent this was 'gitcok'.
It wasn't until just now that I realized that might not be the best choice.
It wasn't until just now that I realized that might not be the best choice.
