<scm>
    <connection>scm:git:git://github.com/msgpack/msgpack-rpc.git</connection>
    <url>scm:git:git://github.com/msgpack/msgpack-rpc.git</url>
  </scm>

Git is quite different in this regard. You can work on five separate logical changes in your working copy — without interacting with the VCS at all — and then build up a series of commits in one fell swoop. Or, you can take the opposite extreme and commit really frequently and mindlessly, returning later to rearrange commits, annotate log messages, squash commits together, tease them apart, or rip stuff out completely. It’s up to you, really. Git doesn’t have an opinion on the matter.

With git you can use the post-commit hook to push after each commit. To do this you'll need to add an executable post-commit script in your .git/hooks directory. For e.g.

So GitHub (and Gitorius, and repo.or.cz) is a place to have the public versions of your repos.

git push origin master

Find a ref that matches master in the source repository (most likely, it would find refs/heads/master), and update the same ref (e.g. refs/heads/master) in origin repository with it. If master did not exist remotely, it would be created.