Commit command using "git add ." about git-work HOT 7 CLOSED

I'd say this kind of thing is a stopper for me.
I sometimes create a few changes as part of my though process, and then commit my changes in different commits, picking which change belongs where. Having to commit all changes in one single commit is for me a no game.
But unfortunately I don't see a way of doing this kind of workflow via command line without loosing efficiency.

from git-work.

@nunopicado I agree with you. We need to commit always a few changes per command. Because this I consider this issue a bug and should be resolved.

But unfortunately I don't see a way of doing this kind of workflow via command line without loosing efficiency.

The problem is adding files typing one by one. If you made many changes in many files may be a hard work to do the job using command line. In that case you can use git gui or we can think in something better...

from git-work.

I go to an extend in which I commit not this or that file, but this or that line in a changed file.
Sometimes the same file has changes which belong in different commits.

from git-work.

In these cases, using command line, we need to use git add -p to decide which lines need to be committed.

from git-work.

Or a GUI! :)

from git-work.

Yeah, of course. In fact I still use git gui and gitk together with the command line.
This project won't try to substitute a GUI. The major goal here is simplicity, effectiveness, and give to the users a flow to work.

from git-work.

Done in 7f825f1.

from git-work.